gitcommitlogger
A Python package that logs the details of a specific set of events made to a GitHub repository. Logs are saved into a CSV file and can optionally be sent in a request to a web app, such as a Google Apps Script attached to a Google Sheet where the data can be stored.
GitHub Actions integration
This package is designed to be used in a GitHub Actions workflow, where the workflow is triggered by a push or pull request to the repository. Details of the commits included in the push will then be logged.
A sample GitHub Actions workflow is included in .github/workflows/event-logger.yml. This example stores the logs into a Google Sheet by first posting them as JSON data to a web app attached to the Google Sheet. The URL of the web app is presumed be stored in a GitHub Actions Secret named COMMIT_LOG_API.
Google Apps Scripts integration
In order to save the logs into a Google Sheet, the following steps are required:
- Create a Google Sheet.
- Attach an Apps Script to the sheet by clicking the
Extensions->Apps Scriptsmenu option in Google Sheets. - Copy/paste the example Apps Script in
apps-script-example/code.jsinto the Apps Script editor and save. This sets up the script as a web app so it can respond toGETorPOSTrequests. - Click the buton to
Deploy->New Deploymentin the Apps Scripts editor. Note the web app URL that is generated once deployed. - Add the URL of the Apps Script web app to the GitHub repository as a secret named
COMMIT_LOG_API. - The
gitcommitloggercommand in the example GitHub Action will send aPOSTrequest to the Google Sheet web app whenever a push or pull request is made on the repository. - The web app will then add a row to the Google Sheet with the details of the commit, including the commit id, author, number of files changed in the commit, number of lines added and deleted.
1 maintainer
Metadata
1 maintainer
Release files for gitcommitlogger 1.2.6
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| gitcommitlogger-1.2.6.tar.gz | 45.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| gitcommitlogger-1.2.6-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 76.8 kB
Release files / gitcommitlogger-1.2.6.tar.gz
| Download URL | gitcommitlogger-1.2.6.tar.gz |
|---|---|
| Size | 45.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
62d178ff69b3977deaddb366619e542a2537bf737bd6ddca2597ea07eaa4560e
|
|
BLAKE2b-256 checksum How to use checksums |
51f6c8002e08e9c91ec7756445413d3e3b40b1ef58d3679b26a4901db08ccaa7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Release files / gitcommitlogger-1.2.6-py3-none-any.whl
| Download URL | gitcommitlogger-1.2.6-py3-none-any.whl |
|---|---|
| Size | 31.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
816fa145fdb4c751757825e47fd449d85d91cf81111afde5cc838cac5babfe4a
|
|
BLAKE2b-256 checksum How to use checksums |
1bea628c05172183b1f3c4175f6cbe387a5fcea25201603f7b003da0d30783b9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Security for gitcommitlogger 1.2.6
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
