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

Revise Github Projects managed by Che teams #22188

Closed
3 tasks done
mkuznyetsov opened this issue May 1, 2023 · 9 comments
Closed
3 tasks done

Revise Github Projects managed by Che teams #22188

mkuznyetsov opened this issue May 1, 2023 · 9 comments
Assignees
Labels
kind/task Internal things, technical debt, and to-do tasks to be performed. status/in-progress This issue has been taken by an engineer and is under active development.

Comments

@mkuznyetsov
Copy link
Contributor

mkuznyetsov commented May 1, 2023

Is your task related to a problem? Please describe

Some of our projects, especially on Che Incubator side, have inconsistent and/or outdated configurations, like permissions to push branches or merge PRs. Ideally, all projects should have the same configuration, when it comes to those things. Codeowners, who would approve these PRs. Updating all these things would help in future, when someone would have to push to those projects

Describe the solution you'd like

  • ensure that list https://github.com/eclipse/che/blob/main/.repositories.yaml is up to date.
  • all eclipse-che/che-incubator repos must have the same configuration:
  • main branch protected from direct pushes,
  • all che org members must have permissions to push branches to the upstream repo,
  • all che org members should be able to merge PRs with at least 1 approved review,
  • merge commits not allowed, to keep the git history linear.
  • every eclipse-che/che-incubator repo should have updated CODEOWNERS file(exact list with repos/owners is TBD).

Describe alternatives you've considered

No response

Additional context

No response

@mkuznyetsov mkuznyetsov added the kind/task Internal things, technical debt, and to-do tasks to be performed. label May 1, 2023
@che-bot che-bot added the status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. label May 1, 2023
@dkwon17 dkwon17 removed the status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. label May 2, 2023
@mkuznyetsov mkuznyetsov self-assigned this May 3, 2023
@mkuznyetsov mkuznyetsov added the status/analyzing An issue has been proposed and it is currently being analyzed for effort and implementation approach label May 3, 2023
@mkuznyetsov mkuznyetsov added status/in-progress This issue has been taken by an engineer and is under active development. and removed status/analyzing An issue has been proposed and it is currently being analyzed for effort and implementation approach labels May 11, 2023
This was referenced May 17, 2023
This was referenced Jun 14, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/task Internal things, technical debt, and to-do tasks to be performed. status/in-progress This issue has been taken by an engineer and is under active development.
Projects
None yet
Development

No branches or pull requests

5 participants