Option to auto-watch on first interaction #3615

New Issue

GiteaMirror · 2025-11-02T05:19:34-06:00

GiteaMirror commented

2025-11-02 05:19:34 -06:00

Originally created by @guillep2k on GitHub (Jul 18, 2019).

Gitea version (or commit ref): Gitea version 1.8.3+2-g11f6ed4 built with go1.12.6 : pam, bindata, sqlite, sqlite_unlock_notify
Git version: 1.8.3.1
Operating system: CentOS 7
Database (use [x]):
- [*] PostgreSQL
- MySQL
- MSSQL
- SQLite
Can you reproduce the bug at https://try.gitea.io:
- Yes (provide example URL)
- No
- Not relevant
Log gist:

In the spirit of AUTO_WATCH_NEW_REPOS, it would be nice to have options to automatically add the user as a watcher on first interactions, like:

AUTO_WATCH_ON_CHANGES = true: any write operation on a server's repository (like push) will subscribe the user to the repository.
AUTO_WATCH_ON_CLONE = true: clone (u other relevant operations) will subscribe the user to the repository.
AUTO_ORG_MEMBER_VISIBLE = true: member is visibile by default.

Originally created by @guillep2k on GitHub (Jul 18, 2019). - Gitea version (or commit ref): Gitea version 1.8.3+2-g11f6ed4 built with go1.12.6 : pam, bindata, sqlite, sqlite_unlock_notify - Git version: 1.8.3.1 - Operating system: CentOS 7 - Database (use `[x]`): - [*] PostgreSQL - [ ] MySQL - [ ] MSSQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [ ] No - [X] Not relevant - Log gist: In the spirit of `AUTO_WATCH_NEW_REPOS`, it would be nice to have options to automatically add the user as a watcher on first interactions, like: - `AUTO_WATCH_ON_CHANGES` = `true`: any write operation on a server's repository (like push) will subscribe the user to the repository. - `AUTO_WATCH_ON_CLONE` = `true`: clone (u other relevant operations) will subscribe the user to the repository. - `AUTO_ORG_MEMBER_VISIBLE` = `true`: member is visibile by default.

GiteaMirror added the type/proposal label 2025-11-02 05:19:34 -06:00

GiteaMirror closed this issue

2025-11-02 05:19:34 -06:00

GiteaMirror commented

2025-11-02 05:19:35 -06:00

@6543 commented on GitHub (Oct 15, 2019):

i think this is related: https://github.com/go-gitea/gitea/issues/8243

@6543 commented on GitHub (Oct 15, 2019): i think this is related: https://github.com/go-gitea/gitea/issues/8243

GiteaMirror commented

2025-11-02 05:19:36 -06:00

@lunny commented on GitHub (Oct 15, 2019):

They should be the same.

@lunny commented on GitHub (Oct 15, 2019): They should be the same.

GiteaMirror commented

2025-11-02 05:19:36 -06:00

@strk commented on GitHub (Oct 28, 2019):

It should be "auto-subscribe", as "watch" is for all activities of a repository ?

@strk commented on GitHub (Oct 28, 2019): It should be "auto-subscribe", as "watch" is for all activities of a repository ?

GiteaMirror commented

2025-11-02 05:19:36 -06:00

@guillep2k commented on GitHub (Oct 28, 2019):

It should be "auto-subscribe", as "watch" is for all activities of a repository ?

@strk My original idea was to watch the entire repo after the users commits/pushes anything to it. It's implemented in #7657, but that PR is not up-to-date.

This is not the same as #7512. This is for subscribing to repos when commiting to them, while #8243 is for subscribing to issues that one creates. Sorry about my lousy description here.

@guillep2k commented on GitHub (Oct 28, 2019): > > > It should be "auto-subscribe", as "watch" is for all activities of a repository ? @strk My original idea was to watch the entire repo after the users commits/pushes anything to it. It's implemented in #7657, but that PR is not up-to-date. This is not the same as #7512. This is for subscribing to repos when commiting to them, while #8243 is for subscribing to issues that one creates. Sorry about my lousy description here.

GiteaMirror commented

2025-11-02 05:19:37 -06:00

@guillep2k commented on GitHub (Nov 30, 2019):

This has been implemented to a satisfactory level. Suscription upon cloning could be implemented as well, but that would be very difficult to do as git has no hook to catch a clone operation (it had one but it was removed long ago).

Closing this.

@guillep2k commented on GitHub (Nov 30, 2019): This has been implemented to a satisfactory level. Suscription upon cloning could be implemented as well, but that would be very difficult to do as git has no hook to catch a clone operation (it had one but it was removed long ago). Closing this.

GiteaMirror commented

2025-11-02 05:19:37 -06:00

@6543 commented on GitHub (Dec 1, 2019):

@guillep2k think this is fine for now :D

@6543 commented on GitHub (Dec 1, 2019): @guillep2k think this is fine for now :D

GiteaMirror referenced this issue

2025-11-02 12:24:22 -06:00

[PR #3615] [MERGED] Log attachment blocked events #17018

Sign in to join this conversation.