-
Notifications
You must be signed in to change notification settings - Fork 275
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
Updating REST API samples and readme files #27
Conversation
aaroncarey
commented
Apr 23, 2018
- Changing the version number throughout: 2.8 -> 3.0
- Minor updates to formatting in README.md
sync aaroncarey-patch-1 to master
Should we be doing a merge with the development branch before opening the PR for master? Looks like they are out of sync. Not sure if that's what we've been doing for this repo. Other repos we typically checki in to the development branch first. |
@d45 I rebased development from master, so they should be in sync now. Agreed that we have typically pushed to development and then merged to master. This is such a small repo though that maybe we should just get rid of the dev branch and use small feature branches like @aaroncarey has been doing. Let's discuss later (and also talk about deleting the already merged patch branches). @aaroncarey this seems fine for today's change. 🚀 When you merge, can you use the squash and merge option? Thanks! |
Sounds good to me. It is a small repo, so simplifying things makes sense. We should definite check with Russ and Lee about the development branch before nuking it. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks good
Thanks to both of you for the review! I'll go ahead and "squash + merge" later this evening when other 2018.1 updates start. And I'll check with Ben / Russell / Lee about the development branch. I have permissions to merge this PR when we are ready to go. |