Skip to content
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

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

ehelms
Copy link
Member

@ehelms ehelms commented Sep 27, 2019

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.

@ekohl
Copy link
Member

ekohl commented Sep 27, 2019

I think the mock commit wasn't intended to be here, correct?

@ehelms
Copy link
Member Author

ehelms commented Sep 27, 2019

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 :)

@ekohl
Copy link
Member

ekohl commented Sep 27, 2019

Github allows draft PRs for this purpose :)

@ehelms
Copy link
Member Author

ehelms commented Sep 27, 2019

Truth .. they need to allow setting that after you open it :/

@ekohl
Copy link
Member

ekohl commented Oct 18, 2019

This now needs a rebase.

@ehelms ehelms changed the title Update spec Add ability to update spec files for nodejs and gems Jan 7, 2020
@zjhuntin
Copy link
Collaborator

zjhuntin commented Jan 8, 2020

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!

@ehelms ehelms force-pushed the update-spec branch 2 times, most recently from 914a882 to dae9765 Compare January 15, 2020 15:50
@ehelms ehelms force-pushed the update-spec branch 4 times, most recently from 5c5203d to ba8a55b Compare March 12, 2020 14:05
@zjhuntin
Copy link
Collaborator

My doubling changelog comment is no longer an issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants