Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
Matrix
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Code
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Container Registry
Model registry
Operate
Environments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Terms and privacy
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
TeDomum
Matrix
Commits
5db2a59a
Unverified
Commit
5db2a59a
authored
4 years ago
by
Richard van der Hoff
Committed by
GitHub
4 years ago
Browse files
Options
Downloads
Patches
Plain Diff
Update CONTRIBUTING.md (#7541)
parent
b2b86990
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
+4
-15
4 additions, 15 deletions
CONTRIBUTING.md
with
4 additions
and
15 deletions
CONTRIBUTING.md
+
4
−
15
View file @
5db2a59a
...
...
@@ -16,21 +16,10 @@ project on github, and then [create a pull request](
https://help.github.com/articles/using-pull-requests/
)
to ask us to pull your
changes into our repo.
**
The single biggest thing you need to know is: please base your changes on
the develop branch -
*not*
master.
**
We use the master branch to track the most recent release, so that folks who
blindly clone the repo and automatically check out master get something that
works. Develop is the unstable branch where all the development actually
happens: the workflow is that contributors should fork the develop branch to
make a 'feature' branch for a particular contribution, and then make a pull
request to merge this back into the matrix.org 'official' develop branch. We
use github's pull request workflow to review the contribution, and either ask
you to make any refinements needed or merge it and make them ourselves. The
changes will then land on master when we next do a release.
Some other things you will need to know when contributing to Synapse:
Some other points to follow:
*
Please base your changes on the
`develop`
branch.
*
Please follow the
[
code style requirements
](
#code-style
)
.
*
Please include a
[
changelog entry
](
#changelog
)
with each PR.
...
...
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