Consider inlining pre-commit update actions

Open
#172 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
50/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Stale
Tech stack
github-actions
Domain
ci-cd

Research direction

Start with .github/workflows/pre-commit-updates.yml at line 22, then compare it with the linked .github/workflows/pre-commit-autoupdate.yml example. Done means the workflow no longer depends on browniebroke/pre-commit-autoupdate-action and performs the intended update job inline.

Written by the indexing model from the issue text.

Description

We use https://github.com/browniebroke/pre-commit-autoupdate-action in the pre-commit updater workflow, but it's actually really simple. Even the author of it seems to have moved on, creating and using their own version that inlines the action in https://github.com/browniebroke/github-actions/blob/main/.github/workflows/pre-commit-autoupdate.yml.

Dominant language
Makefile
Stars
31
Forks
6
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from target/make-python-devex

All issues in target/make-python-devex

Similar issues

More DevOps issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.