-
-
Notifications
You must be signed in to change notification settings - Fork 122
Permalink
Choose a base ref
{{ refName }}
default
Choose a head ref
{{ refName }}
default
Comparing changes
Choose two branches to see what’s changed or to start a new pull request.
If you need to, you can also or
learn more about diff comparisons.
Open a pull request
Create a new pull request by comparing changes across two branches. If you need to, you can also .
Learn more about diff comparisons here.
base repository: styfle/cancel-workflow-action
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: 0.6.0
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
...
head repository: styfle/cancel-workflow-action
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: d7e57e26a6f753933f8ef746a37097a61375236b
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
- 7 commits
- 5 files changed
- 5 contributors
Commits on Dec 24, 2020
-
Configuration menu - View commit details
-
Copy full SHA for b949c16 - Browse repository at this point
Copy the full SHA b949c16View commit details -
feat: default token to GitHub token (#46)
* feat: default token to GitHub token * fix: use quotes for clarity
Configuration menu - View commit details
-
Copy full SHA for 596f393 - Browse repository at this point
Copy the full SHA 596f393View commit details
Commits on Jan 11, 2021
-
Allow matching SHA to be canceled (#50)
Hi, I've started using your action and it is really useful! However, their was one use case for me that was not working: - I have a workflow which temporally build and deploy a version of my app on every `pull_request`. - I have a second workflow which cleanup the temporary deployment on `pull_request: types: [closed]`. - That second workflow call your action to cancel any build runs still running after the PR is closed. The problem is that it will not cancel the latest build run if I merge that commit directly; since they both have the same SHA. So I've added an option `allow_matching_sha` (default to `false`) which can disable that check and allow runs with the same sha on other workflows to be cancelled. So my second workflow looks like this: ```yaml on: pull_request: types: [closed] jobs: cleanup-after-pr-closed: name: Cleanup After PR Closed runs-on: ubuntu-latest steps: - name: Cancel build runs uses: ericmatte/cancel-workflow-action@match-sha with: allow_matching_sha: true workflow_id: '######' ``` Cheers Co-authored-by: Steven <steven@ceriously.com>
Configuration menu - View commit details
-
Copy full SHA for 62b179c - Browse repository at this point
Copy the full SHA 62b179cView commit details -
Configuration menu - View commit details
-
Copy full SHA for 99e363e - Browse repository at this point
Copy the full SHA 99e363eView commit details
Commits on Jan 12, 2021
-
Configuration menu - View commit details
-
Copy full SHA for 277e407 - Browse repository at this point
Copy the full SHA 277e407View commit details -
Configuration menu - View commit details
-
Copy full SHA for dfbe605 - Browse repository at this point
Copy the full SHA dfbe605View commit details -
Configuration menu - View commit details
-
Copy full SHA for d7e57e2 - Browse repository at this point
Copy the full SHA d7e57e2View commit details
Loading
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff 0.6.0...d7e57e26a6f753933f8ef746a37097a61375236b