rticommunity / rticommunity/rticonnextdds-examples
Problems with GH Actions
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 148
- Forks
- 153
- PR merge metrics
- No merged PRs in 30d
Description
What is the current behavior?
Secrets cannot be shared in Pull Requests workflows.
Steps to reproduce the issue
Take a look of #349 (you can see in the steps the secret is empty). Also, we tried to reproduce the issue in another repo.
More information
Secrets are environment variables that are encrypted. Anyone with collaborator access to this repository can use these secrets for Actions.
Secrets are not passed to workflows that are triggered by a pull request from a fork.
In this thread you can also get more information.
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.
Research direction
Start by reviewing issue #349 and the linked example pull request to confirm how the secret is empty in a pull request workflow. Read the linked GitHub Community thread for the documented fork-secret behavior, then determine whether a repository-side change is possible; the issue does not currently define a clear completion condition.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100