For developers
Contribute back
For developers, if you would like to contribute back to this repository, consider forking the original repo and creating a pull request:
Fork the original repo to a personal or lab account.
Clone the fork to your local system, to a different place than where you ran your analysis.
Copy the modified files from your analysis to the clone of your fork, e.g.,
cp -r workflow path/to/fork
. (Make sure to not accidentally copy config file contents or sample sheets. Instead, manually update the example config files if necessary)Commit and push your changes to your fork.
Create a pull request against the original repository.
Obtain updates from upstream
Whenever you want to synchronize your workflow copy with new developments from upstream, do the following.
Once, register the upstream repository in your local copy:
git@github.com:snakemake-workflows/54gene-olink.git
orgit remote add -f upstream https://github.com/snakemake-workflows/54gene-olink.git
if you do not have setup ssh keys.Update the upstream version:
git fetch upstream
Create a diff with the current version:
git diff HEAD upstream/master workflow > upstream-changes.diff
Investigate the changes:
vim upstream-changes.diff
Apply the modified diff via:
git apply upstream-changes.diff
Carefully check whether you need to update the config files:
git diff HEAD upstream/master config
. If so, do it manually, and only where necessary, since you would otherwise likely overwrite your settings and samples.