Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Synchronize project metadata with GitHub #8

Open
3 tasks done
bswck opened this issue Jan 29, 2024 · 4 comments
Open
3 tasks done

Synchronize project metadata with GitHub #8

bswck opened this issue Jan 29, 2024 · 4 comments

Comments

@bswck
Copy link
Contributor

bswck commented Jan 29, 2024

Goal

Periodically synchronize metadata for each downstream project with its GitHub repository.

Motivation

Enhanced integration with GitHub, long-term host of all downstream OSS projects:

  • More informative GitHub layout thanks to repository descriptions
  • Better navigation: automatic project URLs (my suggestion is RTD links whenever possible—from the README docs badge?)
  • Community flow: Discord webhooks tracked in Set up automatic Discord webhook registration #11
  • GitHub Topics (those under the website URL—from Trove classifiers?)

@jaraco Have I included everything? 😀


Derived from discussions @ jaraco/pytest-perf#10.

@bswck
Copy link
Contributor Author

bswck commented Jan 29, 2024

I initially wanted to use GitHub CLI for achieving the goal, but after a closer inspection I am more into extending the jaraco.develop.github.GitHub class with methods implementing explicit API endpoint calls.

@bswck
Copy link
Contributor Author

bswck commented Jan 29, 2024

During project metadata synchronization, PyPI project URLs could also be maintained in setup.cfg.
It would probably be useful to see links to documentation or issue tracker right in PyPI project pages.

@jaraco
Copy link
Owner

jaraco commented Feb 29, 2024

Perhaps out of scope for this issue, but a related concern I'd like to consider (somewhere) is how to manage best practices in the GitHub project. For example, I find I need to configure these settings manually in each project:

image

Ideally, there'd be a centralized way to manage these settings across projects too. Perhaps the "org" hierarchy could provide better defaults and obviate the need to manage the settings across all projects.

@jaraco
Copy link
Owner

jaraco commented Aug 15, 2024

Perhaps the "org" hierarchy could provide better defaults and obviate the need to manage the settings across all projects.

Turns out this is not the case. Even after forming coherent-oss, I've found that these settings have to be set manually on each and every project.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants