Skip to content

Build: Support jquery-release --dry-run flag #4498

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

Merged
merged 1 commit into from
Oct 5, 2019
Merged

Conversation

mgol
Copy link
Member

@mgol mgol commented Oct 4, 2019

Summary

Without this change passing --dry-run to jquery-release still pushes to the
jquery-dist repository which is dangerous as one can assume --dry-run to be
safe from external side effects.

Checklist

Sorry, something went wrong.

Without this change passing `--dry-run` to jquery-release still pushes to the
jquery-dist repository which is dangerous as one can assume `--dry-run` to be
safe from external side effects.
@mgol mgol added this to the 3.5.0 milestone Oct 4, 2019
@mgol mgol requested a review from timmywil October 4, 2019 14:46
@mgol mgol self-assigned this Oct 4, 2019
Copy link
Member

@dmethvin dmethvin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Gack! Yes.

Copy link
Member

@timmywil timmywil left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sounds good. I guess I never ran into a problem because I always changed the dist remote.

@mgol mgol merged commit d7d0b52 into jquery:master Oct 5, 2019
@mgol mgol deleted the dry-run branch October 5, 2019 16:48
@mgol mgol removed the Needs review label Oct 5, 2019
mgol added a commit that referenced this pull request Oct 5, 2019
Without this change passing `--dry-run` to jquery-release still pushes to the
jquery-dist repository which is dangerous as one can assume `--dry-run` to be
safe from external side effects.

Close gh-4498

(cherry picked from commit d7d0b52)
@mgol
Copy link
Member Author

mgol commented Oct 5, 2019

Landed on master at d7d0b52 & on 3.x-stable at c7a5e1b.

@lock lock bot locked as resolved and limited conversation to collaborators Apr 2, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Development

Successfully merging this pull request may close these issues.

3 participants