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

Allow using master as a lock target #80

Merged
merged 1 commit into from
Apr 27, 2020
Merged

Conversation

schneems
Copy link
Contributor

Currently hatchet lock locks all repos to a specific commit, but there are times where a maintainer wants the latest commit instead of a specific version. For example if the ruby buildpack maintainer wanted to make sure that the ruby-getting-started app.

Currently `hatchet lock` locks all repos to a specific commit, but there are times where a maintainer wants the latest commit instead of a specific version. For example if the ruby buildpack maintainer wanted to make sure that the `ruby-getting-started` app.
@schneems schneems force-pushed the schneems/master-lock branch from 07c83bf to 7eab2eb Compare April 27, 2020 17:47
@schneems schneems merged commit 12c2951 into master Apr 27, 2020
@schneems schneems deleted the schneems/master-lock branch April 27, 2020 17:53
@schneems schneems restored the schneems/master-lock branch April 27, 2020 17:53
schneems added a commit to heroku/heroku-buildpack-python that referenced this pull request Apr 27, 2020
jkutner pushed a commit to heroku/heroku-buildpack-python that referenced this pull request Apr 27, 2020
@edmorley edmorley deleted the schneems/master-lock branch August 27, 2020 08:44
dryan pushed a commit to dryan/heroku-buildpack-python that referenced this pull request Nov 19, 2020
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.

1 participant