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
This is just an idea. But I'm always afraid to create PR for the master branch.
According to A successful Git branching model, the master branch should point out the latest release.
We consider origin/master to be the main branch where the source code of HEAD always reflects a production-ready state.
Keep the master branch as same as the latest release on npm. and use the develop branch for future release
master
develop
xdpm does not have develop branch
N/A
The text was updated successfully, but these errors were encountered:
kerrishotts
dkstevekwak
No branches or pull requests
This is just an idea. But I'm always afraid to create PR for the master branch.
According to A successful Git branching model, the master branch should point out the latest release.
Expected Behaviour
Keep the
master
branch as same as the latest release on npm.and use the
develop
branch for future releaseActual Behaviour
xdpm does not have
develop
branchReproduce Scenario (including but not limited to)
N/A
Steps to Reproduce
N/A
Platform and Version
N/A
Sample Code that illustrates the problem
N/A
Logs taken while reproducing problem
N/A
The text was updated successfully, but these errors were encountered: