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
0946d509
Commit
0946d509
authored
2 years ago
by
syuilo
Browse files
Options
Downloads
Patches
Plain Diff
Update CONTRIBUTING.md
parent
bb3c6785
No related branches found
Branches containing commit
No related tags found
Tags containing commit
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
CONTRIBUTING.md
+8
-6
8 additions, 6 deletions
CONTRIBUTING.md
with
8 additions
and
6 deletions
CONTRIBUTING.md
+
8
−
6
View file @
0946d509
...
...
@@ -71,13 +71,15 @@ For now, basically only @syuilo has the authority to merge PRs into develop beca
However, minor fixes, refactoring, and urgent changes may be merged at the discretion of a contributor.
## Release
For now, basically only @syuilo has the authority to release Misskey.
However, in case of emergency, a release can be made at the discretion of a contributor.
### Release Instructions
1.
commit version changes in the
`develop`
branch (
[
package.json
](
https://github.com/misskey-dev/misskey/blob/develop/package.json
)
)
2.
follow the
`master`
branch to the
`develop`
branch.
3.
Create a
[
release of GitHub
](
https://github.com/misskey-dev/misskey/releases
)
1.
Commit version changes in the
`develop`
branch (
[
package.json
](
https://github.com/misskey-dev/misskey/blob/develop/package.json
)
)
2.
Create a release PR.
-
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.
-
Assign about 2~3 reviewers.
3.
The release PR is approved, merge it.
4.
Create a
[
release of GitHub
](
https://github.com/misskey-dev/misskey/releases
)
-
The target branch must be
`master`
-
The tag name must be the version
...
...
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