maliput / maliput/maliput_infrastructure
CI: Update path to repositories when using actions/checkout action
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 2
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
This targets all the repos in the maliput ecosystem
### Summary
We are using
```sh
- uses: actions/checkout@v2
with:
repository: ToyotaResearchInstitute/maliput
fetch-depth: 0
path: ${{ env.ROS_WS }}/src/maliput
token: ${{ secrets.MALIPUT_TOKEN }}
```
for each dependency.
Let's use `maliput/maliput` instead of `ToyotaResearchInstitute/maliput`
### Alternative
We could directly handle it via `dependencies.repos` file and remove all the `actions/checkout` actions making the workflow a bit simpler.
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 by locating the workflow files containing the actions/checkout snippets for the maliput dependencies, then inspect the dependencies.repos file mentioned as an alternative. Update the repository paths consistently across the targeted repositories and verify that the workflows still check out dependencies into the expected workspace locations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, shell
- Domain
- ci-cd, devops
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100