Skip to content

Skip duplicate actions when pushing in this repository - #45

Merged
diazona merged 1 commit into
masterfrom
avoid-duplicate-actions/1/dev
Jul 18, 2022
Merged

Skip duplicate actions when pushing in this repository#45
diazona merged 1 commit into
masterfrom
avoid-duplicate-actions/1/dev

Conversation

@diazona

@diazona diazona commented Jul 14, 2022

Copy link
Copy Markdown
Contributor

Currently when someone pushes a branch directly to pytest-localserver, we get two copies of each Github action, one for the push and one for the pull request. This change should skip the pull_request action for branches pushed directly into this repository. It won't affect branches coming from other people's forks.

@diazona diazona added this to the v0.7.0 milestone Jul 14, 2022
@diazona
diazona requested a review from redtoad July 14, 2022 07:52
@diazona

diazona commented Jul 14, 2022

Copy link
Copy Markdown
Contributor Author

...evidently this doesn't work :/ I'll have to figure it out later.

@diazona diazona mentioned this pull request Jul 15, 2022
Currently when someone pushes a branch directly to pytest-localserver,
we get two copies of each Github action, one for the push and one for
the pull request. This change should skip the pull_request action for
branches pushed directly into pytest-localserver. It won't affect
branches coming from other people's forks.
@diazona
diazona force-pushed the avoid-duplicate-actions/1/dev branch from c86d1e8 to 0e0ce0c Compare July 17, 2022 08:48
@diazona
diazona merged commit fae08fe into master Jul 18, 2022
@diazona
diazona deleted the avoid-duplicate-actions/1/dev branch July 18, 2022 00:38
diazona added a commit to diazona/setuptools-pyproject-migration that referenced this pull request Jul 8, 2023
Currently when creating a pull request (at least, one not in a fork, but
at the moment there are no forks anyway), we get two copies of each
Github action, one for the branch push and one for the pull request.
The change in this commit should skip the action running for the pull
request whenever the source branch exists locally in this repository.
It shouldn't affect branches coming from other people's forks, if there
are forks in the future.

I copied the logic to do this from another project in which I worked out
how to do the same thing:
  pytest-dev/pytest-localserver#45
The comment I've added to the workflow refers to a blog post I relied on
when figuring out how to make this work for that other project.
diazona added a commit to diazona/setuptools-pyproject-migration that referenced this pull request Jul 9, 2023
Currently when creating a pull request (at least, one not in a fork, but
at the moment there are no forks anyway), we get two copies of each
Github action, one for the branch push and one for the pull request.
The change in this commit should skip the action running for the pull
request whenever the source branch exists locally in this repository.
It shouldn't affect branches coming from other people's forks, if there
are forks in the future.

I copied the logic to do this from another project in which I worked out
how to do the same thing:
  pytest-dev/pytest-localserver#45
The comment I've added to the workflow refers to a blog post I relied on
when figuring out how to make this work for that other project.
diazona added a commit to diazona/setuptools-pyproject-migration that referenced this pull request Jul 9, 2023
Currently when creating a pull request (at least, one not in a fork, but
at the moment there are no forks anyway), we get two copies of each
Github action, one for the branch push and one for the pull request.
The change in this commit should skip the action running for the pull
request whenever the source branch exists locally in this repository.
It shouldn't affect branches coming from other people's forks, if there
are forks in the future.

I copied the logic to do this from another project in which I worked out
how to do the same thing:
  pytest-dev/pytest-localserver#45
The comment I've added to the workflow refers to a blog post I relied on
when figuring out how to make this work for that other project.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant