We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
In https://epiverse-trace.github.io/blueprints/git-branching-merging.html the "real package" is mentioned. Why not call it "released package"?
The text was updated successfully, but these errors were encountered:
oh it's an example name 😂 I was confused, I'm leaving this open in case it's useful.
Sorry, something went wrong.
regarding development workflows, you might be interested in http://r-multiverse.org/
No branches or pull requests
In https://epiverse-trace.github.io/blueprints/git-branching-merging.html the "real package" is mentioned. Why not call it "released package"?
The text was updated successfully, but these errors were encountered: