-
Notifications
You must be signed in to change notification settings - Fork 218
New issue
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
Keeping Docs Consistent with Features #27
Comments
I would suggest using git-flow https://datasift.github.io/gitflow/IntroducingGitFlow.html |
I really like that workflow, it makes a lot of sense. Thank you for sharing that! And that's a good point about releases. No point in trying to force things out the door every Sunday. So moving to the GitFlow methodology:
Am I missing anything? |
Yeah that all sounds good 👍 |
Awesome! Check out #30 with the updated documentation. Does this mean the existing PRs need to be rebased off of develop so that they can be merged in to that branch instead of master? And thank you for your help with this! Really wish I knew about GitFlow months ago! |
Yeah that would be the best thing to do. I have changed my PR's |
Perfect, thank you! |
#17 looks great and ready to merge into master, but that would update the documentation on getpapercss.com, but would the downloadable css file would not have the updates. That would need to be rebuilt and put into a release. This causes an issue of the documentation not matching the available features if downloaded.
Would it be best to keep a separate branch for what gets shown on getpapercss.com, instead of just using the master branch? That way the most up to date features are in the master, but the download/documentation match up online. Every Sunday could be a release day where the new features are built and released via Github releases, and the website is updated to match.
Does anyone have any thoughts or experience with the best workflow to follow here?
The text was updated successfully, but these errors were encountered: