we have a GitHub action which is below, setup to run the deployment step for a release. However whenever we create a release it creates 3 GitHub actions jobs rather than one. I’m not clear if it’s a GitHub bug or incorrect logic in the GitHub action (most likely)

is it possible to have a github action deploy to dev environment every time main is pushed to and then have a manual option that has a list of environment to choose from to deploy too using one job? My idea would be that there logic to pass to say if push to main then env is dev and if manual trigger then use what input was passed (test, dev, prod, etc…)

Is it possible to get the last merged PR on the main branch inside a workflow? I want to run test coverage during commit, and fail the PR check if the test coverage is going down. For that I need the coverage from the last merged PR in main.

I wanted to create multiple folders within a folder (in GitHub) for our team. For instance, under my manager there are 5 colleagues, and each colleague may have multiple projects in hand.

I have a reusable workflow which I use to build and push images. I’m trying to create a certificate file in the first relevant step (which works), however the file isn’t accessible in the next step for some reason.

I created a GitHub Organization with 10 Repositories. Eeach of them has own CI/CD GitHub Actions Pipeline.

I currently have a workflow which calls a custom Action which creates a Job Summary by writing to the GITHUB_STEP_SUMMARY variable. My goal is to display this markdown text not in the Workflow summary but rather in a seperate job which only contains said text.

I currently have a workflow which calls a custom Action which creates a Job Summary by writing to the GITHUB_STEP_SUMMARY variable. My goal is to display this markdown text not in the Workflow summary but rather in a seperate job which only contains said text.

In Gitlab and Bitbucket, we can add manual step in pipeline. is there any way we can do same thing in a Github action?

I am using reusable workflow in GitHub Actions. Any idea why this workflow job in my feature.yml file: