Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
R
Rosekey
Manage
Activity
Members
Labels
Plan
Issues
0
Issue boards
Milestones
Iterations
Wiki
Requirements
Code
Merge requests
0
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Locked files
Build
Pipelines
Jobs
Pipeline schedules
Test cases
Artifacts
Deploy
Releases
Package Registry
Container Registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Code review analytics
Issue analytics
Insights
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
freelynetwork
Rosekey
Commits
c6e0430a
Unverified
Commit
c6e0430a
authored
2 years ago
by
syuilo
Committed by
GitHub
2 years ago
Browse files
Options
Downloads
Patches
Plain Diff
Update CONTRIBUTING.md
parent
065aa0f9
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
CONTRIBUTING.md
+8
-1
8 additions, 1 deletion
CONTRIBUTING.md
with
8 additions
and
1 deletion
CONTRIBUTING.md
+
8
−
1
View file @
c6e0430a
...
...
@@ -66,6 +66,13 @@ Be willing to comment on the good points and not just the things you want fixed
-
Are there any omissions or gaps?
-
Does it check for anomalies?
## Deploy
The
`/deploy`
command by issue comment can be used to deploy the contents of a PR to the preview environment.
```
/deploy sha=<commit hash>
```
An actual domain will be assigned so you can test the federation.
## Merge
For now, basically only @syuilo has the authority to merge PRs into develop because he is most familiar with the codebase.
However, minor fixes, refactoring, and urgent changes may be merged at the discretion of a contributor.
...
...
@@ -77,7 +84,7 @@ However, minor fixes, refactoring, and urgent changes may be merged at the discr
-
Into
`master`
from
`develop`
branch.
-
The title must be in the format
`Release: x.y.z`
.
-
`x.y.z`
is the new version you are trying to release.
3.
~~
Deploy and perform a simple QA check. Also verify that the tests passed.
~~ (TODO)
3.
Deploy and perform a simple QA check. Also verify that the tests passed.
4.
Merge it.
5.
Create a
[
release of GitHub
](
https://github.com/misskey-dev/misskey/releases
)
-
The target branch must be
`master`
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment