-
Notifications
You must be signed in to change notification settings - Fork 6
Workflow for updating `accessibility.sty`
I intend to follow the gitflow process described by Scott Chacon at http://scottchacon.com/2011/08/31/github-flow.html.
This is probably connected to a specific bug or feature request. Again, following the guidance from Scott:
To work on something new, create a descriptively named branch off of master (ie: new-oauth2-scopes)
Commit to that branch locally and regularly push your work to the same named branch on the server
I suggest creating a new directory in the samples folder for whatever branch / pull is being tested. You may want to use the branch or issue name for the directory so you don't go crazy, for example article_supportFancyHeader
or article_issue16
.
You can then hand-edit copies of accessibility.sty
in that directory during the development process.
Once everything works, modify access.tex
and run batch.tex
to bring source/accessibility.sty
up to date, and replace the local copy with a link to source/accessibility.sty
.
This is a bit messy but I am not sure how else to do it.
Following the guidance from Scott Chacon,
When you need feedback or help, or you think the branch is ready for merging, open a pull request