Support for github assets based on branches/revisions
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
Research direction
Search the cookbook for the github_asset implementation and trace how tag-based assets are currently resolved. Review the existing Octokit usage, if present, and define how a branch or revision should identify the needed files. Done means assets can be retrieved from a branch or revision without creating a release, with tests or documentation covering the new behavior.
Written by the indexing model from the issue text.
Description
: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.
- Dominant language
- Ruby
- Stars
- 25
- Forks
- 25
- Avg merge
- 5h 40m
- Merged PRs (30d)
- 1
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from sous-chefs/github
-
Feature Request
Difficulty 3/5 1-2 days Newbie friendliness 45/100
sous-chefs/github#47 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 38/100
sous-chefs/github#46 ·
-
Dependency Dashboard Open
Difficulty 1/5 Under an hour Newbie friendliness 15/100
sous-chefs/github#26 ·
-
Bug
Difficulty 2/5 1-3 hours Newbie friendliness 48/100
sous-chefs/github#9 · 2 comments ·
All issues in sous-chefs/github
Similar issues
-
user-reported
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Kong/developer.konghq.com#7316 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
TheOdinProject/curriculum#31408 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
notch8/utk_knapsack#148 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 78/100
Homebrew/homebrew-cask#288729 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100