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

Support for github assets based on branches/revisions #19

Open
DragosDumitrache opened this issue Jul 18, 2022 · 1 comment
Open

Support for github assets based on branches/revisions #19

DragosDumitrache opened this issue Jul 18, 2022 · 1 comment
Labels
Feature Request Enhancement to existing functionality or new functionality

Comments

@DragosDumitrache
Copy link

:person_frowning: Problem Statement

Currently, github_asset seems to only support getting assets based on a tag, which involves a release happening. If I wanted to test a feature across repos, I would have to cut a new release from that feature branch, or that feature branch being merged into HEAD, updating the revision tag for the cookbook, running my integration tests, and repeat the cycle if any issues crop up.

❔ Possible Solution

Add support for specifying a branch/revision and using octokit to check out the code and the needed files at that point in time, as an alternative to tags.

⤴️ Describe alternatives you've considered

The alternative would be a draft release, which is something I'll trial shortly, but it still involves a potential draft release for something that might not be ready.

I'd love to get your thoughts on the matter though, and whether this is feasible or not.

@DragosDumitrache DragosDumitrache added the Feature Request Enhancement to existing functionality or new functionality label Jul 18, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature Request Enhancement to existing functionality or new functionality
Projects
None yet
Development

No branches or pull requests

2 participants
@DragosDumitrache and others