check, which ci workflows will be triggered after your push
Project description
pre-push
check what CI workflows are gonna be triggered after your push
How it works
basically we are taking every modified file path, and check if it matches to any of the path-strings in the current git repository workflows
workflows location
yaml files in .github/workflows/ directory
changed files
changed files are the one, which are added to the latest commit from the previous commit
usage
run the prepush command, from anywhere in the git repository
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Source Distribution
Built Distribution
Filter files by name, interpreter, ABI, and platform.
If you're not sure about the file name format, learn more about wheel file names.
Copy a direct link to the current filters
File details
Details for the file prepush-1.1.0.tar.gz.
File metadata
- Download URL: prepush-1.1.0.tar.gz
- Upload date:
- Size: 3.3 kB
- Tags: Source
- Uploaded using Trusted Publishing? No
- Uploaded via: twine/4.0.2 CPython/3.12.1
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 |
f7a6193be8e6f7c8ec2029385710fd6592433fdc17aa2f937aed9c459f6b8c07
|
|
| MD5 |
ddba724c09746f6a0c9c0ba41db27fac
|
|
| BLAKE2b-256 |
4ec4ad9bb6f491877c6a152c84acbd316cf4c7c1a4afd42b338a34c94994afb7
|
File details
Details for the file prepush-1.1.0-py3-none-any.whl.
File metadata
- Download URL: prepush-1.1.0-py3-none-any.whl
- Upload date:
- Size: 4.4 kB
- Tags: Python 3
- Uploaded using Trusted Publishing? No
- Uploaded via: twine/4.0.2 CPython/3.12.1
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 |
dbf82cfc6326e954012d5b5d9e77da547a592c5bd59bf13074ab4672a3a22980
|
|
| MD5 |
14c40e801713b3d5edd099fb76f9717c
|
|
| BLAKE2b-256 |
68d9f02d3d2064e6bc41c4abcbcc6cc4d487ae47e22017d4236ef6d6b8089c6c
|
