Modification Timekeeper
Keep modification time in a Markdown file's YAML front matter up to date.
Usage as a pre-commit hook
Add the following to your .pre-commit-config.yaml file:
- repo: https://github.com/stefmolin/modification-timekeeper
rev: 0.1.2
hooks:
- id: modification-timekeeper
You can also configure the name of the last modified field (--field-name), which field to put the modified field after it it doesn't already exist (--after-key), whether to use UTC (--as-utc), and the number of seconds after which the modified time in the file is considered stale (--tolerance):
- repo: https://github.com/stefmolin/modification-timekeeper
rev: 0.1.2
hooks:
- id: modification-timekeeper
args: [--field-name=modified, --after-key=publication_date, --as-utc, --tolerance=30]
Be sure to check out the pre-commit documentation for additional configuration options.
Contributing
Please consult the contributing guidelines.
1 maintainer
Release files for modification-timekeeper 0.1.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| modification_timekeeper-0.1.2.tar.gz | 15.5 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| modification_timekeeper-0.1.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 20.7 kB
Release files / modification_timekeeper-0.1.2.tar.gz
| Download URL | modification_timekeeper-0.1.2.tar.gz |
|---|---|
| Size | 15.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
432eb086574774cca71576d4bd2c7a4b21490b9dec46af12251f64187a16f016
|
|
BLAKE2b-256 checksum How to use checksums |
8fef6b3a6f777161a60ac7b262fb4121b3c8b28a894cb43556f098f802b66706
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 4, 2025.
Transparency logRelease files / modification_timekeeper-0.1.2-py3-none-any.whl
| Download URL | modification_timekeeper-0.1.2-py3-none-any.whl |
|---|---|
| Size | 5.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
73bf2b4987cc6c4b75779b8ca191630646b094a00e0dea41cf82cc8158b7bfb6
|
|
BLAKE2b-256 checksum How to use checksums |
d7706e76acbc0fb8dd18c9d3dd76930beec8e5d301437bd5ffdcea26702bdd87
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 4, 2025.
Transparency log
