-
Notifications
You must be signed in to change notification settings - Fork 13
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
Add ability to update spec files for nodejs and gems #207
base: master
Are you sure you want to change the base?
Conversation
I think the mock commit wasn't intended to be here, correct? |
Yes and no. It is not required but while I iterate on any design updates, it's helpful for me to have both the mock and update-spec commands handy locally at the same time :) |
Github allows draft PRs for this purpose :) |
Truth .. they need to allow setting that after you open it :/ |
f624e8e
to
eb1d546
Compare
This now needs a rebase. |
The only thing that this might not do properly is I think that it does doubles up on the changelog instead of printing it once. Everything else, at least for the gems, seems to work properly! |
914a882
to
dae9765
Compare
5c5203d
to
ba8a55b
Compare
My doubling changelog comment is no longer an issue. |
9d2dd13
to
ef2a486
Compare
This includes another PR thats required. This adds the ability to update just the spec file of a package (for NPM and Gems) and thus do it en masse. The playbook is a bit messy and I am willing to break it up depending on how folks feel about the design.