Updated the weekly chores list to include various server maintenance responsibilities on Andy. This addition ensures Prometheus, Grafana, and Greylog checks, enhancing accountability and coverage for these services.
"Ducky" has been removed from the weekly chores list as it was deemed unnecessary and redundant. This simplifies the checklist and reduces confusion. No significant impacts expected.
Included new servers 'Zwergente' and 'Smaragdente' to the chores list to ensure complete coverage of chores. This update helps maintain accuracy and comprehensiveness in the schedule.
Reassigned server updates from 'Chalmers' and 'Grimey' to 'Pekingente'. Removed 'Grimey' from the task list to reflect current server management. This helps streamline responsibilities and ensures up-to-date representation of server assignments.
Added new tasks to the weekly chores list including Mautrix-Meta for Instagram and Bifröst under the assigned user 'Lard Lad'. This ensures all relevant maintenance activities are documented and tracked effectively.
Added Flanders, H08, and H09 to the weekly chore checklist and assigned new tasks to them. This update ensures all tasks are properly distributed among team members, improving workload management.
Switched the Weekly Chores pipeline path in the README from `scripts/chores.py` to `.forgejo/workflows/chores.yml`.
This change ensures the documentation accurately reflects the current location of the pipeline configuration. No functionality changes are involved.
Expands README with information about the purpose of the repository,
specifically detailing the pipelines it contains. Adds a link to
Private.coffee and descriptions of the weekly chores pipeline to
make the repository's functionality clearer to new users.
- Initialized .gitignore to exclude virtual environment
- Added a comprehensive chores checklist as a markdown file
- Introduced development dependencies (ruff, black) in requirements-dev.txt
- Updated chores script to read tasks from the markdown file instead of an environment variable, improving task organization and maintainability
Uncommented the cron job in the chores workflow configuration, setting
it to run automatically at noon every Friday. This change facilitates
regular, automated maintenance tasks without manual intervention.
Updated `.forgejo/workflows/chores.yml` to use `vars` context for
environment variables, ensuring consistent variable scoping and improved
maintainability. This change simplifies the way variables are managed in
GitHub Actions workflow.
Ensured that the 'due_date' variable is now formatted in strict ISO 8601
compliance by removing microseconds and appending 'Z' to indicate UTC.
This change aids in consistent date-time parsing across different
systems and services that expect a standardized timestamp without
fractional seconds.
Introduce a debug print statement to log the payload before creating an
issue in the `chores.py` script. This aids in tracing outgoing data and
facilitates easier troubleshooting of the issue creation process.
Refactor the authentication in the chore script by removing the 'token'
field from the payload and including it in the header as
'Authorization'. This change enhances security practices by aligning
with standard HTTP authorization protocols.
Refactored the assignment of FORGEJO_URL to use a more idiomatic fallback approach in case the environment variable is not set. This change ensures that None values are handled correctly and the default URL is used when the environment variable FORGEJO_URL is undefined, enhancing reliability.
Refactored the chores script to improve the robustness of environment
variable handling. This includes mandatory checks for the FORGEJO_TOKEN
and default values or prompts for missing optional environment
variables. Added assertion to ensure the token is present after
retrieval which, combined with the KeyError, will provide better error
handling. Optional variables now use a fallback value directly in the
get method for concise expression.
Resolves issue with silent failures when required environment settings
are not provided.
Casting `CHORES_EXPIRY_DAYS` environment variable to int ensures that
the expiry days value is correctly interpreted for use throughout the
application without type errors. This small but critical change
guarantees consistent behavior when dealing with time-based logic. No
issue reference provided.
Introduced a set of environment variables in the CI workflow
configuration to align with the chores script's requirements. The
workflow now passes explicit values for necessary variables, matching
the environment variable name changes in the chores script for
consistency and clarity. Ensured correct token usage by updating TO
token reference. This change facilitates better configuration management
and error handling in automated tasks.
compatibility
Updated the environment variable for authentication to align with the
pipeline's token-naming conventions, improving integration and
consistency across our automated workflows. Error messaging reflects
this change for clarity during troubleshooting.
Adds a repository checkout step in the chores CI workflow to ensure code
is available for subsequent chore automation tasks. This update enables
the proper execution of the automated script for generating chores
issues.
Updated the trigger event for the chores workflow from on commit to on
push to ensure the workflow runs whenever code is pushed to the
repository. This enhances automation by aligning the execution of
routine tasks with code integration practices.
Implemented a new Forgejo Action workflow to automatically create weekly
chores issues based on a Python script. This workflow triggers on
commits and the Python script uses project-specific environment
variables to customize the issue creation, including setting due dates
and assigning users. Streamlines project maintenance and ensures regular
task management.
