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

rename net29 -> net #15

Merged
merged 1 commit into from
Jan 20, 2025
Merged

rename net29 -> net #15

merged 1 commit into from
Jan 20, 2025

Conversation

dietmarkuehl
Copy link
Collaborator

No description provided.

@dietmarkuehl dietmarkuehl merged commit a827741 into main Jan 20, 2025
5 checks passed
@dietmarkuehl dietmarkuehl deleted the rename-net29-into-net branch January 20, 2025 22:56
@neatudarius
Copy link
Member

Link to bemanproject/beman#85

Copy link
Member

@neatudarius neatudarius left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM 👍

Btw, I noticed net & execution repos do not have review rules enforced. I change the repo settings.

@dietmarkuehl
Copy link
Collaborator Author

So you are saying I'll need to get my changes reviewed? I'm certainly not against reviews. Probably means I'll need to adjust my workflow.

@neatudarius
Copy link
Member

neatudarius commented Jan 21, 2025

So you are saying I'll need to get my changes reviewed? I'm certainly not against reviews. Probably means I'll need to adjust my workflow.

Short answer yes, but I don't want to cause trouble if you have something urgent.

When I closed bemanproject/beman#67, I was pretty sure that all repos had these rules enforced. Yesterday I noticed they were missing from net / execution, I my intuition was to re-apply the settings.

Currently, these repos have CODEOWNERS == "Dietmar + David + Darius". Feel free to extend the list. I am happy to help with review from time to time. I think you said at some point about onboarding more people into this code. CODEOWNERS files is one way to do it :D (but ofc, it will raise opinions and may sometimes slow down the process).

Let me know if you want to have an exception for your repos.

@dietmarkuehl
Copy link
Collaborator Author

I don't think there are currently any active collaborators. Thus, getting code reviews may be tricky. I wouldn't be surprised if that is a common pattern, at least for projects under development. Of course, we'd like to get all code reviewed.

Currently, at least net lets me override the restriction (I'm not sure what the state of execution is). It is probably worth discussing how we want to handle that. I'll add an item to the agenda. ...or should it be a Discourse?

@neatudarius
Copy link
Member

neatudarius commented Jan 21, 2025

I don't think there are currently any active collaborators. Thus, getting code reviews may be tricky. I wouldn't be surprised if that is a common pattern, at least for projects under development. Of course, we'd like to get all code reviewed.

Currently, at least net lets me override the restriction (I'm not sure what the state of execution is). It is probably worth discussing how we want to handle that. I'll add an item to the agenda. ...or should it be a Discourse?

Please open a thread on discourse - next meeting is reserver for the website discussion. Also link bemanproject/beman#67 on that thread. Meanwhile, you are admin on both repos and you can merge any PR with extra permissions. I would like to keep the rules anyways for other contributors, to be reviewed at least by Dietmar or other codeowners. TLDR: at least now we add more control for outsider contributors, and still letting you to use "fast merge" :D

@dietmarkuehl
Copy link
Collaborator Author

I don't think there are currently any active collaborators. Thus, getting code reviews may be tricky. I wouldn't be surprised if that is a common pattern, at least for projects under development. Of course, we'd like to get all code reviewed.
Currently, at least net lets me override the restriction (I'm not sure what the state of execution is). It is probably worth discussing how we want to handle that. I'll add an item to the agenda. ...or should it be a Discourse?

Please open a thread on discourse - next meeting is reserver for the website discussion. Also link bemanproject/beman#67 on that thread. Meanwhile, you are admin on both repos and you can merge any PR with extra permissions. I would like to keep the rules anyways for other contributors, to be reviewed at least by Dietmar or other codeowners. TLDR: at least now we add more control for outsider contributors, and still letting you to use "fast merge" :D

Well, I can't merge the PR renaming execution26 to execution: I can't get to the extra permission thing on the UI. I'm not sure what is missing.

@neatudarius
Copy link
Member

neatudarius commented Jan 21, 2025

Well, I can't merge the PR renaming execution26 to execution: I can't get to the extra permission thing on the UI. I'm not sure what is missing.

refresh and try again please (I forgot to specify exception for admins :D)

image

@dietmarkuehl
Copy link
Collaborator Author

Now it worked! Thanks!

I have landed the change and updated the name. There is stil a bit. residual work to update net and lazy (and a few branches). I hope to do that tomorrow.

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 this pull request may close these issues.

2 participants