-
Notifications
You must be signed in to change notification settings - Fork 75
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
FR: Ability to bypass owner checks #18
Comments
This is something that did come up in the early days of golink and we discussed it briefly. I've worked at companies that had both models, and don't necessarily have strong feelings about it, but we did settle on enforcing ownership. A few things that I think are really helpful if you don't enforce ownership are email notifications when someone edits your link and/or an edit history so you can see what was changed. We don't have either one of those right now. My last company was the no-enforced-ownership model, so I initially advocated for that. However in practice, we haven't found the ownership to be much of an issue. Occasionally, I'll message someone asking that they update a golink or change ownership, and it's pretty straightforward. Would you be willing to try it for a little while and see how much of a problem is ends up being? |
Hi folks,
Thanks for putting this together, it's incredible!
We're using this in a smaller company, and would like the ability to opt-out of ownership checks when editing links. At our scale (<10 engs) it's somewhat more useful to let anyone change these.
Ideally this would be a checkbox during the golink creation, thinking we can iterate towards there. Useful crawl solution can be a global flag to opt-out of the checks (a la
-skip-ownership-checks
).Happy to take this on if you think it's directionally right.
The text was updated successfully, but these errors were encountered: