variablelab/theatre
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

Update CONTRIBUTING.md branch naming conventions (#106)

Browse source
This commit is contained in:
Elliot 2022-03-23 08:05:03 -04:00 committed by GitHub
parent 139c3ed556
commit 89133c5e6f
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 3 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
CONTRIBUTING.md
View file

@ -217,4 +217,6 @@ We use Github's regular PR workflow. Basically fork the repo, push your commits,
If you're a core contributor and have write access to the repo, you should submit your pull requests from a branch If you're a core contributor and have write access to the repo, you should submit your pull requests from a branch
rather than a personal fork. The naming convention for these branches should be: rather than a personal fork. The naming convention for these branches should be:
* `(feature|hotfix)/[identifier]` * `(feature|hotfix|docs)/[identifier]`
or
* an autogenerated branch name from a Github issue (On an issue without a PR, look under the "Development" sidebar heading for a "create a branch link")