research-software-ecosystem / research-software-ecosystem/content
Committing bioschemas right after creating
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 48
- Forks
- 35
- Avg merge
- 19m
- Merged PRs (30d)
- 887
Description
We might need to put more work in this github action. It creates bioschemas on every pull-request and tries to push it to origin Head. Then it's getting 403 from github, because actions bot from PR owner doesn't have enough rights to push. I guess, it would be better to create new pull requests with bioschemas on every push. With auto generated PRs we would have more control of situation and we can clearly see if something goes wrong.
Ping @bgruening @matuskalas @hmenager
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/workflows/bioschemas-build.yml, especially the step around line 47 that pushes generated Bioschemas to origin. Trace when the workflow runs on pull requests and pushes, then determine how generated changes can be submitted as new pull requests without relying on the PR author's permissions. Done means the workflow no longer receives a 403 while providing a visible pull request for generated Bioschemas.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100