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.

Sign up for GitHub

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

Jump to bottom

feat: use repository cache for release builds #116

Merged
merged 1 commit into from
Jan 20, 2022
Merged

feat: use repository cache for release builds #116

merged 1 commit into from
Jan 20, 2022

Conversation

kormide
Copy link
Member

@kormide kormide commented Jan 16, 2022

No description provided.

@kormide kormide requested a review from f0rmiga January 16, 2022 21:34
@kormide
Copy link
Member Author

kormide commented Jan 16, 2022

I suppose the only way to test this is to actually tag a release?

@kormide kormide force-pushed the release-cache-key branch 2 times, most recently from 3345e76 to a872588 Compare January 17, 2022 23:45
@f0rmiga
Copy link
Contributor

f0rmiga commented Jan 19, 2022

I suppose the only way to test this is to actually tag a release?

Please, do not release. My review is enough. We already validated the changes in the PR pipeline.

@kormide kormide requested a review from f0rmiga January 19, 2022 18:33
@f0rmiga f0rmiga merged commit fe327c8 into main Jan 20, 2022
@f0rmiga f0rmiga deleted the release-cache-key branch January 20, 2022 00:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@f0rmiga f0rmiga Awaiting requested review from f0rmiga

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@kormide @f0rmiga