Github Action: can’t access to a file through a shared github action
I have a shared workflows and actions repo, that is used by another organization repositories, one of that actions, it’s responsible to set env vars which are defined on a repository local file, that is located on .github/variables/local-vars.env on Repo1:
Start GihHub workflow with API
I’m trying to start a GitHub workflow using GitHub’s API as documented
here https://docs.github.com/en/rest/actions/workflows?apiVersion=2022-11-28#create-a-workflow-dispatch-event
How to control the name of a reusable workflow?
I am trying to call a reusable workflow but the name of the workflow in GitHub Actions tab is always {caller_job}/{reusable_job}
:
How to control the name of a reusable workflow?
I am trying to call a reusable workflow but the name of the workflow in GitHub Actions tab is always {caller_job}/{reusable_job}
:
How to control the name of a reusable workflow?
I am trying to call a reusable workflow but the name of the workflow in GitHub Actions tab is always {caller_job}/{reusable_job}
:
How to control the name of a reusable workflow?
I am trying to call a reusable workflow but the name of the workflow in GitHub Actions tab is always {caller_job}/{reusable_job}
:
How to control the name of a reusable workflow?
I am trying to call a reusable workflow but the name of the workflow in GitHub Actions tab is always {caller_job}/{reusable_job}
:
How can I configure Dependabot to allow it access to other repositories within the same corporate GitHub organization?
I have a repository within a corporate GitHub organization that uses Dependabot to keep its GitHub Actions dependencies up-to-date, including reusable workflows:
Only trigger workflow if it is coming from a specific branch [duplicate]
This question already has answers here: Use `on` to filter by source and target branch for PR (2 answers) Closed 3 months ago. Given the following branches: main feature_1 feature_important_1 feature_2 feature_3 feature_important_2 feature_4 To trigger pipelines from any branch to branches named *_important_*, we can use: name: “some_name” on: pull_request: branches: – ‘*_important_*’ But […]
Only trigger workflow if it is coming from a specific branch [duplicate]
This question already has answers here: Use `on` to filter by source and target branch for PR (2 answers) Closed 3 months ago. Given the following branches: main feature_1 feature_important_1 feature_2 feature_3 feature_important_2 feature_4 To trigger pipelines from any branch to branches named *_important_*, we can use: name: “some_name” on: pull_request: branches: – ‘*_important_*’ But […]