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

Why? #3

Open
numberZero opened this issue Feb 17, 2023 · 0 comments
Open

Why? #3

numberZero opened this issue Feb 17, 2023 · 0 comments

Comments

@numberZero
Copy link

This appears to be a weird self-modifying repository. What... are the reasons behind this?

Basically, I see several problems.

  1. Storing benchmark results in a Git repository. Looks like abuse. No wait, this is abuse. Not big resource-wise but definitely a wrong way to use Git.
  2. Keeping the harness separate of the primary repository. This is not a metadeployment collecting 100500 other repos, it only grabs two and with minetest#13034, would only need one.
  3. Having code committing to a repository in that same repository. Follows from points 1 and 2 but even then, with these new shiny “fine-grained access tokens” that shouldn’t be necessary.
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

No branches or pull requests

1 participant