neume-network / neume-network/data
checkout step for neume-network/core wrongfully assumes that if neume-network/data@branchname is run, that branch is available on neume-network/core@branchname too
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 15
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
- https://github.com/neume-network/data/blob/c05e8eafc8f2b078096b8a7d088fab7d725c3b64/.github/actions/run_step/action.yml#L39
- e.g. here I tried debugging some custom action we're building but core doesn't have the branch name: https://github.com/neume-network/data/runs/7995476885?check_suite_focus=true#step:3:131
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Start with .github/actions/run_step/action.yml at line 39 and reproduce the behavior using the linked workflow run. Trace how the checkout step derives the branch name across neume-network/data and neume-network/core. Done means the action no longer assumes that a matching branch exists in core when running a data branch.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100