search

snorkel-team / snorkel

A system for quickly generating training data with weak supervision
https://snorkel.org
Apache License 2.0
5.81k stars 857 forks source link

Persist branches for stable releases #1503

Closed chaturv3di closed 5 years ago

chaturv3di commented 5 years ago

For my specific use-case, I'd like to git clone the repo and build it locally. For this purpose, it would be immensely helpful if you could persist the (latest) stable release branches.

If you were developing as per the git-flow workflow, then master would be the latest stable release and all the nightly-builds could go in the develop branch.

I could clone the entire repo and checkout the stable version based on tags, but I guess persisting those branches makes better sense.

Your thoughts?

henryre commented 5 years ago

Hi @chaturv3di, thanks for the question! We've adopted a source control workflow which works well for open-source projects that use continuous integration and is based on Github Flow. As you pointed out, we use tags to mark stable releases. If your goal is to not checkout the full repo history, you can use the --branch argument for git clone, which works with tags as well. Closing for now, feel free to reopen if you have more questions.