b-robotized / b-robotized/ros_team_workspace
[Templates] CI configuration for binary builds
Open
- Dominant language
- Shell
- Stars
- 150
- Forks
- 29
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 3
Description
It probably makes sense to investigate the following:
- separate builds against `main` and `testing` repositories.
- use "allow-failure" on `testing` builds (when this is resolved actions/runner#2347
Contributor guide
Research direction
Locate the CI configuration templates for binary builds and review how builds currently target the main and testing repositories. Check the referenced actions/runner#2347 issue before deciding how testing failures should be handled; done means the two repository targets are separated and testing failures are allowed as specified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, shell
- Domain
- build-system, ci-cd
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100