Here's a thread of code-repository questions I've had while at PyCon. Feel free to boost them or reply to them, I'm doing them one at a time specifically so discussions will start
Here's a thread of code-repository questions I've had while at PyCon. Feel free to boost them or reply to them, I'm doing them one at a time specifically so discussions will start
Is there a method yet for ensuring every repo in an org has a set of issue/PR labels? I wrote https://pypi.org/project/epithet/ for this years ago, and am wondering if I need to update it or if better solutions have emerged.
The concept of "org labels" exists, but only gets applied to NEW repos created.
@phildini @bitprophet One thing I appreciate about copier over some of them is that it accepts a subdirectory for the template, so you can even colocate it with a repository that has different rules: https://github.com/WorldconVotingSystems/nomnom/blob/main/copier.yml
I’ve even managed (in that repo) to tie it into automated testing.
@phildini @Codeberg https://forgejo.org/docs/latest/user/profile/
I believe README is the only one that's picked up by the software, but you can include other info and link it.
@phildini In the past I've used GitHub Actions to sync labels from a file to a repo:
https://github.com/termcolor/termcolor/blob/main/.github/labels.yml
https://github.com/termcolor/termcolor/blob/main/.github/workflows/labels.yml
But I expect it's much easier via a `gh` command now.
#GitHub #GitHubActions #ghCLI