-
Notifications
You must be signed in to change notification settings - Fork 26
Editing Process
Craig Shoemaker edited this page Oct 27, 2015
·
3 revisions
The editing process will vary slightly depending on if you have commit rights or not. For local forks in either case preferably run the grunt verify
(found in the assets/tools/checker
folder of the repository) task to check for broken links/images before committing the changes.
If you do not have commit rights to the repository, then you can submit changes via a pull request. Once your request is received then a team member will work with you to edit the topic to make it publish-ready.
For those with commit rights, please read Contributing & Making Changes then you will:
- Create a branch for your new or edited topic
- Commit changes to that branch
- Create an issue and assign it to the person responsible for review
- Once approved then you copy or merge the changes in your temporary branch to the appropriate production branches
- Delete your editing branch