Force new collaborators to watch the repo #5064

Open
opened 2025-11-02 06:13:00 -06:00 by GiteaMirror · 3 comments
Owner

Originally created by @kbzowski on GitHub (Mar 15, 2020).

I would like to force new collaborators to watch the particular repository.
It can be done either as an option in app.ini or I could do it myself by custom webhook (but AFAIK nothing is fired when new collaborator is added)

Originally created by @kbzowski on GitHub (Mar 15, 2020). I would like to force new collaborators to watch the particular repository. It can be done either as an option in app.ini or I could do it myself by custom webhook (but AFAIK nothing is fired when new collaborator is added)
GiteaMirror added the type/proposal label 2025-11-02 06:13:00 -06:00
Author
Owner

@guillep2k commented on GitHub (Mar 16, 2020):

Can this be used to send SPAM? I guess it's no different from org teams, however...

@guillep2k commented on GitHub (Mar 16, 2020): Can this be used to send SPAM? I guess it's no different from org teams, however...
Author
Owner

@kbzowski commented on GitHub (Mar 17, 2020):

I see, that I need to clarify few things.
I'm against preventing someone from stopping watching a repository. My proposal is only that the new collaborator could have "watch" enabled by default and and still keep a possibility to "unwatch" at any time. SPAM could be a huge problem, but this approach allow easily stop it.
And, of course, this option will be off by default in config and will require the administrator to turn it on intentionally.

In case of our team, we manage to collaborate without using org teams, which are great tool, but not required for each case.

I'm open to another opinion, of course.

@kbzowski commented on GitHub (Mar 17, 2020): I see, that I need to clarify few things. I'm against preventing someone from stopping watching a repository. My proposal is only that the new collaborator could have "watch" enabled by default and and still keep a possibility to "unwatch" at any time. SPAM could be a huge problem, but this approach allow easily stop it. And, of course, this option will be off by default in config and will require the administrator to turn it on intentionally. In case of our team, we manage to collaborate without using org teams, which are great tool, but not required for each case. I'm open to another opinion, of course.
Author
Owner

@guillep2k commented on GitHub (Mar 18, 2020):

If it's off by default and the config docs come with a warning notice, then it should be OK.

@guillep2k commented on GitHub (Mar 18, 2020): If it's off by default and the config docs come with a warning notice, then it should be OK.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#5064