#1939: 2021-02-01 tasks

[x] run update.py to check for derivative file fix (https://github.com/cu-mkp/manuscript-object/issues/70)
[x] create set of instructions for changing any derivative files (see comment below)
[x] unit testing --> is https://github.com/cu-mkp/manuscript-object/issues/51 (code checks as developing manuscript-object)
[x] regression testing by updating travis --> #1941 (checks AFTER update.py is run)
[x] automated checks of metadata (from last time) --> https://github.com/cu-mkp/manuscript-object/issues/48 (entry-metadata has complete and accurate values, which can be dealt with at either stage, either at level of https://github.com/cu-mkp/manuscript-object/issues/51 and #1941)
[x] review DCE redesign
[x] https://github.com/cu-mkp/manuscript-object/issues/68 (release of manuscript-object) --> later
[x] open issues? set priorities
[x] travis CI shenanigans - #1942 and #1947
[x] add to READ.me files how to properly run update.py using a branch

njr2128 commented:

@gschare will create place to put this: making changes to derivative files in m-k-manuscript-data: cd [m-k-manuscript-data] git fetch git pull git checkout -b [name of branch] {checkout a branch} cd [manuscript-object] git fetch git pull python(+version) update.py cd [m-k-manuscript-data] git add . git commit -m ‘#[issue##]: [commit message]’ git push -u origin [branchname]

gschare commented:

Maybe put this in a README.md in the root of the repo?

Making changes to derivative files in m-k-manuscript-data:

cd to m-k-manuscript-data directory
git fetch
git pull
Checkout a branch: git checkout -b [name of branch]
cd to manuscript-object directory
git fetch
git pull
Run update.py: python3 update.py (might need to use python3.8, e.g., if you have more than one version installed)
cd back to m-k-manuscript-data directory
git add .
git commit -m '#[issue##]: [commit message]'
git push -u origin [name of branch]

#1939: 2021-02-01 tasks

opened by njr2128

njr2128 commented:

gschare commented:

njr2128 commented: