feat: granular watch settings with event filtering and author exclusions #21

Merged

pat-s merged 59 commits from feat/granular-watch-settings-clean into v14.0/forgejo-codefloe 2026-03-03 09:22:20 +00:00

Conversation 2 Commits 59 Files changed 64 +3208 -295

pat-s commented 2026-01-30 21:25:44 +00:00

Owner

Copy link

Summary

This PR adds granular control over repository watch notifications, allowing users to:

• Filter by event type: Choose which events trigger notifications (Issues, Pull Requests, Releases)
• Exclude specific authors: Prevent notifications from certain users globally or per-repository
• Exclude bot accounts: Automatically filter out bot activity from notifications

## Summary This PR adds granular control over repository watch notifications, allowing users to: - **Filter by event type**: Choose which events trigger notifications (Issues, Pull Requests, Releases) - **Exclude specific authors**: Prevent notifications from certain users globally or per-repository - **Exclude bot accounts**: Automatically filter out bot activity from notifications

pat-s added 2 commits 2026-01-30 21:25:44 +00:00

feat: add granular watch settings for repositories ... 2eb4ec5312

This adds the ability to select which types of events to receive notifications
for when watching a repository:
- Issues
- Pull requests
- Releases

Changes:
- Add WatchEventType bitmask to track event preferences in watch table
- Add migration (v14b) to add watch_events column
- Update watch UI with dropdown to select event types
- Add user settings page for default watch preferences
- Add API support for setting watch events
- Add DefaultWatchEvents instance setting
- Add e2e and integration tests

Users can now customize their watch preferences per-repository instead of
an all-or-nothing approach.

feat: add author exclusions to watch notifications ... a515ffb03f

Allow users to exclude specific authors from generating watch notifications.
Supports global exclusions (configured in user settings), per-repo exclusions
(configured in watch dropdown), and automatic bot user exclusion.

Exclusions are applied when creating issue/PR notifications and sending
release emails.

pat-s requested review from Cyborus 2026-01-30 21:25:45 +00:00

pat-s added 2 commits 2026-01-30 21:40:14 +00:00

refactor: replace bot exclusion with regex pattern matching ... 3b77646869

- Remove "Exclude bot accounts" checkbox option
- Add regex pattern field to match usernames to exclude (e.g., .*\[bot\]$)
- Fix user search dropdown to use /user/search_candidates endpoint
- Update all callers to pass author name for pattern matching

fix: add missing locale strings for notification settings ... 84bdd90313

Add success messages for auto-watch and default watch events settings.
Remove unused per_repo_help locale string.

pat-s added 1 commit 2026-01-30 21:50:07 +00:00

chore: regenerate swagger spec for watch API changes 5053b61c57

pat-s added 2 commits 2026-01-30 21:59:00 +00:00

fix: correct octicon-clock SVG viewBox attribute ... 91b11def98

The SVG had duplicate viewBox attributes (0 0 16 16 and 0 0 24 24).
The first one took precedence but the path data is designed for 24x24,
causing the icon to be cut off at the bottom right.

fix: initialize user search dropdowns after htmx swaps ... 3139f4f4ce

The inline scripts weren't executing after htmx content swaps.
Move dropdown initialization to htmx.js using data attributes
and htmx:afterSettle event handler.

pat-s added 1 commit 2026-01-30 22:07:03 +00:00

fix: properly initialize user search dropdowns on page load ... 6ec56707ec

- Export initUserSearchDropdowns from htmx.js
- Call it from index.js onDomReady to ensure proper timing
- Move window.config access inside function to avoid timing issues
- Use document.addEventListener for htmx events (bubbles from body)

pat-s referenced this pull request from a commit 2026-01-30 22:33:00 +00:00

docs: add PR #21 (granular watch settings) to README

pat-s added 3 commits 2026-01-30 22:33:00 +00:00

docs: add PR #21 (granular watch settings) to README 7a8c8e2b30

fix(ui): align repo icon with repo name on explore page ... 6d9cb6b3d1

Add baseline alignment for flex-item-leading to align the repo icon
horizontally with the repo name text, matching the pattern used for
flex-item-icon.

fix(ui): improve repo icon alignment using matched line-height ... 4383b86ee2

Replace baseline alignment approach with matched dimensions:
- .flex-item-leading: min-height: 1.5rem with align-items: center
- .flex-item-title: line-height: 1.5rem

Both containers now have the same 24px height, ensuring icons
(both 20px SVGs and 24px avatars) align with text centers.
Uses relative units (rem) for robustness.

Cyborus commented 2026-01-30 23:24:57 +00:00

First-time contributor

Copy link

Oh, uh, hi! I guess it makes sense that CODEOWNERS works on cross-instance forks.

Oh, uh, hi! I guess it makes sense that `CODEOWNERS` works on cross-instance forks.

pat-s commented 2026-01-31 08:58:24 +00:00

Author

Owner

Copy link

Ah sorry, will take care this is being removed.

Ah sorry, will take care this is being removed.

👍 1

pat-s removed review request for Cyborus 2026-01-31 08:58:29 +00:00

pat-s added 1 commit 2026-01-31 08:59:39 +00:00

lint b4abf8d09f

pat-s added 1 commit 2026-01-31 13:58:29 +00:00

fix(test): use specific selector for issue title Save button ... 2c5f966741

The test was failing because getByText('Save') now matches both the
issue title editor Save button and the watch settings Save button.
Use a more specific selector targeting the button with data-update-url
inside #issue-title-editor.

pat-s added 1 commit 2026-01-31 15:42:49 +00:00

feat: add participating and @mentions watch option ... 37a548499a

Add a fourth watch event type for "Participating and @mentions" which
only triggers notifications when the user is participating in the
issue/PR (author, assignee, mentioned, or has commented).

Changes:
- Add WatchEventParticipating constant (value: 8)
- Add WatchEventDefault constant set to WatchEventParticipating
- Update GetWatchEvents() to return WatchEventDefault instead of All
- Add WatchesParticipating() method to WatchEventType
- Add UI checkbox for participating option in watch settings
- Update user notification settings to include participating default
- Rename "Issues" to "All issues" and "Pull requests" to "All pull
  requests" in locale to distinguish from participating mode

This option is combinable with other watch options (Issues, PRs,
Releases) and is the new implicit default for new watches.

pat-s added 1 commit 2026-01-31 16:11:59 +00:00

fix(ui): close watch dropdown before htmx swap to prevent flash ... 2632fa78de

Close the details dropdown immediately when clicking Save or Unwatch,
before the htmx request is made. This prevents the visible layout
flash that occurred when the dropdown content was being swapped
while still visible.

pat-s added 1 commit 2026-01-31 16:17:58 +00:00

feat(ui): auto-save watch settings when toggling checkboxes ... 1e46a22878

- Checkboxes now auto-save on change without requiring Save button
- Dropdown stays open so users can toggle multiple options
- Removed Save button (no longer needed with auto-save)
- Unwatch button remains for completely unwatching

pat-s added 1 commit 2026-01-31 16:22:43 +00:00

fix(ui): use morph swap to eliminate flash on watch settings toggle ... 81e34c6725

Use idiomorph's morph:outerHTML swap instead of plain outerHTML.
This performs smart DOM diffing and only updates elements that
actually changed, eliminating the visible flash when toggling
checkboxes.

pat-s added 1 commit 2026-01-31 16:56:44 +00:00

fix(ui): use hx-swap=none to eliminate flash on checkbox toggle ... a382f14954

Instead of swapping DOM content after auto-save, just return 204
No Content. The checkbox state is already updated by the browser,
so no DOM manipulation is needed. This completely eliminates the
flash issue.

pat-s added 1 commit 2026-02-01 13:02:10 +00:00

fix: eliminate flash/flicker in watch settings dropdown ... 410e71e7c2

- Add no-loading-indicator CSS class to disable htmx loading styles
- Use hx-swap="none" with 204 response for seamless auto-save
- Handle unwatch via client-side updates to avoid DOM morphing issues
- Store locale strings in data attributes for client-side text updates

pat-s added 1 commit 2026-02-01 13:16:47 +00:00

fix: add button text update handler on checkbox change ... a34ea0ab22

The hx-on::after-request handler updates the button text between
"Watch" and "Watching" based on whether any checkbox is selected.

pat-s added 1 commit 2026-02-01 22:10:57 +00:00

fix: unwatch all unchecks all checkboxes and prevents race condition ... 1a7cb434c7

- Unwatch now unchecks ALL checkboxes (not just some)
- Add data-skip-trigger flag to prevent form's change handler from
  interfering with unwatch button's UI updates
- Form's after-request handler skips when skip flag is set

pat-s added 1 commit 2026-02-01 22:23:09 +00:00

fix: use server-side rendering for watch button toggle ... 550b2d0607

Replace unreliable htmx from:find trigger with JavaScript-based approach:
- Add initWatchCheckboxes() to handle checkbox change events
- Trigger htmx form submission programmatically on change
- Server returns full HTML with correct Watch/Watching text
- Remove complex client-side text manipulation logic

pat-s added 2 commits 2026-02-01 23:57:28 +00:00

fix: reduce webpack parallelism for macOS compatibility ... cbcb4a08b4

Add parallelism: 5 and filesystem caching to webpack config to avoid
EMFILE "too many open files" errors on macOS with default ulimit of 1024.

fix(watch): submit form on dropdown close instead of each checkbox change ... 01454935db

Previously, the watch dropdown would submit the form on every checkbox
change, causing the dropdown to flash/reload after each click. This made
it difficult to make multiple changes at once.

Changes:
- Use idiomorph (hx-swap="morph:outerHTML") to preserve dropdown state
- Submit form only when dropdown closes (not on each checkbox change)
- Track changes using form state comparison to avoid unnecessary submits
- Use MutationObserver pattern (like tippy.js/dirauto.js) for initialization
- Show empty checkboxes when not watching instead of user defaults

The dropdown now stays open while making multiple selections, and only
submits when the user closes it (if changes were made).

pat-s added 1 commit 2026-02-02 08:30:10 +00:00

fix(lint): use import.meta.filename instead of fileURLToPath ... 5ebebb50b9

ESLint unicorn/prefer-import-meta-properties rule requires using
import.meta.filename instead of fileURLToPath(import.meta.url).

pat-s force-pushed feat/granular-watch-settings-clean from 84f2e51217 to 9b242ee807 2026-02-02 10:03:46 +00:00 Compare

pat-s force-pushed feat/granular-watch-settings-clean from ae9e27a64b to 67cb67fb0f 2026-02-03 11:14:47 +00:00 Compare

pat-s added 2 commits 2026-02-04 22:36:01 +00:00

feat: filter email notifications by watch event type settings ... e552c28692

Email notifications now respect the granular watch event settings
(Issues, PRs, Releases). Add GetRepoWatchersIDsForEvent() to filter
watchers by event type and update mailer paths for issues/PRs/releases.

feat: filter UI notifications by watch event type settings ... bf2051fdbe

UI notifications now respect the granular watch event settings.
Update notification_list.go and uinotification/notify.go to use
GetRepoWatchersIDsForEvent() for filtering by Issues/PRs.

pat-s force-pushed feat/granular-watch-settings-clean from 1d73a12943 to 67253db25f 2026-02-04 23:13:57 +00:00 Compare

pat-s force-pushed feat/granular-watch-settings-clean from 67253db25f to 00a2038f40 2026-02-04 23:21:21 +00:00 Compare

pat-s added 2 commits 2026-02-04 23:49:12 +00:00

feat: add UI notifications for releases ... 9740131073

Add a codefloe-specific release notification system that creates
UI notifications for users who have subscribed to release events.

- Create new ReleaseNotification model in models/codefloe/
- Add migration v4 to create release_notification table
- Add NewRelease handler to uinotification service that creates
  notifications for watchers with release events enabled

feat: add UI for release notifications ... 050aba7f10

Add a web interface to view and manage release notifications:

- Add routes for release notifications listing, status changes, and purge
- Add ReleaseNotifications, ReleaseNotificationStatusPost, and
  ReleaseNotificationPurgePost handlers
- Create notification_releases.tmpl and notification_releases_div.tmpl
  templates
- Add "Releases" tab to main notification page with unread count badge
- Include release notifications in total notification count
- Add CountReleaseNotifications and MarkReleaseNotificationAsUnread
  functions to the model
- Add "releases" translation key to locale

pat-s added 1 commit 2026-02-05 09:59:01 +00:00

refactor: integrate release notifications into unified list ... 81879b7061

Show release notifications alongside issue/PR notifications in the
main "unread" tab instead of a separate tab:

- Create UnifiedNotification wrapper struct to handle both types
- Merge both notification types into a single sorted list
- Update template to render both types inline
- Combine counts for accurate total unread badge
- Update status handler to support both notification types
- Update purge to mark both types as read
- Remove separate release notification routes and templates

pat-s added 1 commit 2026-02-05 10:07:35 +00:00

fix: compute total notification count in Go instead of template ... 5072284dee

The template 'add' function doesn't exist in Forgejo. Move the
addition to the Go middleware where we already have access to
both counts.

pat-s added 1 commit 2026-02-05 10:14:52 +00:00

fix: include release notifications in navbar bell icon count ... 268d1cd2f0

Update the navbar template to use TotalNotificationUnreadCount
which includes both issue and release notifications, with a
fallback to NotificationUnreadCount for compatibility.

pat-s force-pushed feat/granular-watch-settings-clean from 9865d928df to 5bd5120155 2026-02-15 21:25:44 +00:00 Compare

pat-s force-pushed feat/granular-watch-settings-clean from 5bd5120155 to 4bc223f9a6 2026-02-15 21:55:20 +00:00 Compare

pat-s force-pushed feat/granular-watch-settings-clean from 4bc223f9a6 to fb8c00f91a 2026-02-15 22:21:28 +00:00 Compare

pat-s force-pushed feat/granular-watch-settings-clean from fb8c00f91a to f773312e9f 2026-02-15 22:40:46 +00:00 Compare

pat-s force-pushed feat/granular-watch-settings-clean from f773312e9f to 0046536529 2026-02-15 23:27:07 +00:00 Compare

pat-s added 1 commit 2026-03-01 10:13:32 +00:00

Merge branch 'v14.0/forgejo-codefloe' into feat/granular-watch-settings-clean a1260298c1

pat-s force-pushed feat/granular-watch-settings-clean from 8b5918e139 to c3dfe52114 2026-03-01 12:11:09 +00:00 Compare

pat-s force-pushed feat/granular-watch-settings-clean from c3dfe52114 to ea6aa13761 2026-03-02 15:17:49 +00:00 Compare

pat-s added 1 commit 2026-03-02 15:45:20 +00:00

fix: render WatchesParticipating and excluded users on initial page load ... a67ba15969

The watch settings dropdown was missing WatchesParticipating, ExcludedUserIDs, and ExcludedUsers template data during the initial repo page load (in RepoAssignment). These were only set in loadWatchContext which is called by htmx action handlers, not on full page renders. This caused the "Participating and @mentions" checkbox to always appear unchecked on page load, even when enabled in the database, leading to stale watch_events values when other checkboxes were toggled.

Also fixes the ExcludedUserIDs xorm column name mapping (GonicMapper was mapping it to excluded_user_i_ds instead of excluded_user_ids) by adding an explicit column name tag.

Removes temporary debug logging from notification creation and UI notification handlers.

pat-s added 2 commits 2026-03-02 18:13:30 +00:00

test: add coverage for granular watch filtering and form round-trip ... 1f3baec99f

Add unit tests for FilterUserIDsByWatchParticipating and GetRepoWatchersIDsForEvent to verify event-based filtering with varied watch_events bitmasks. Add unit tests for UpdateWatchSettings covering new watch creation, event updates, and excluded user ID storage. Add integration test for the watch settings form round-trip to prevent regressions on the WatchesParticipating template data bug.

fmt fce1a6fea5

pat-s added 1 commit 2026-03-02 18:26:27 +00:00

lint 71f778b376

pat-s added 1 commit 2026-03-02 19:05:17 +00:00

chore: remove dead code flagged by deadcode linter ... 19518fd80a

Remove unused CreateReleaseNotification (only the batch variant CreateReleaseNotificationsForUsers is called) and unused GetRepoWatchersIDs (superseded by GetRepoWatchersIDsForEvent).

pat-s force-pushed feat/granular-watch-settings-clean from b795770d83 to c14ab9d14d 2026-03-02 20:39:43 +00:00 Compare

pat-s added 1 commit 2026-03-02 21:12:19 +00:00

fix: update TestRepoGetReviewers unit test for new watch fixtures ... 501fac93e9

New watchers (user13, user14) on repo1 appear as eligible reviewers in the public repo reviewer query.

pat-s added 12 commits 2026-03-02 22:10:39 +00:00

[v14.0/forgejo] fix: improve SQLite "database is locked" errors by increasing default SQLITE_TIMEOUT (#11220) ... b3c7fbcce3

**Backport:** https://codeberg.org/forgejo/forgejo/pulls/11179

As noted in https://codeberg.org/forgejo/forgejo/issues/10900#issuecomment-10339634, `TestAPICreateIssueParallel` is failing intermittently in Forgejo CI.  Based upon this intermittent failure, I've made these changes:
- Increase the parallel run of the test from 10 instances to 100, which caused this test to fail consistently and reliably on my dev workstation.  The test execution time at 100 parallel invocations is only ~4 seconds.
- Increase the default `SQLITE_TIMEOUT` from 500ms to 60s, which caused this test to succeed consistently in CI.

Co-authored-by: Mathieu Fenniak <mathieu@fenniak.net>
Reviewed-on: https://codeberg.org/forgejo/forgejo/pulls/11220
Reviewed-by: Mathieu Fenniak <mfenniak@noreply.codeberg.org>
Reviewed-by: Michael Kriese <michael.kriese@gmx.de>
Co-authored-by: forgejo-backport-action <forgejo-backport-action@noreply.codeberg.org>
Co-committed-by: forgejo-backport-action <forgejo-backport-action@noreply.codeberg.org>

[v14.0/forgejo] fix: when expanding a dynamic matrix, original 'needs' access was lost (#11166) ... 8ef91fa1cc

**Backport:** #11164

Manual backport required due to conflicts with recent workflow expansion work.

(cherry picked from commit c7d23fa6e8)

<!--start release-notes-assistant-->

## Release notes
<!--URL:https://codeberg.org/forgejo/forgejo-->
- Bug fixes
  - [PR](https://codeberg.org/forgejo/forgejo/pulls/11166): <!--number 11166 --><!--line 0 --><!--description Zml4OiB3aGVuIGV4cGFuZGluZyBhIGR5bmFtaWMgbWF0cml4LCBvcmlnaW5hbCAnbmVlZHMnIGFjY2VzcyB3YXMgbG9zdA==-->fix: when expanding a dynamic matrix, original 'needs' access was lost<!--description-->
<!--end release-notes-assistant-->

Reviewed-on: https://codeberg.org/forgejo/forgejo/pulls/11166
Reviewed-by: Andreas Ahlenstorf <aahlenst@noreply.codeberg.org>
Co-authored-by: Mathieu Fenniak <mathieu@fenniak.net>
Co-committed-by: Mathieu Fenniak <mathieu@fenniak.net>

[v14.0/forgejo] fix(ui): prevent label overflow in PR CI checks on mobile (#11327) ... 677de6419b

**Backport:** https://codeberg.org/forgejo/forgejo/pulls/11287

Fix #11266

Co-authored-by: panc <pan0xc@foxmail.com>
Reviewed-on: https://codeberg.org/forgejo/forgejo/pulls/11327
Reviewed-by: 0ko <0ko@noreply.codeberg.org>
Co-authored-by: forgejo-backport-action <forgejo-backport-action@noreply.codeberg.org>
Co-committed-by: forgejo-backport-action <forgejo-backport-action@noreply.codeberg.org>

Update module github.com/go-chi/chi/v5 to v5.2.4 [SECURITY] (v14.0/forgejo) (#11397) ... 41c3c5bb80

Reviewed-on: https://codeberg.org/forgejo/forgejo/pulls/11397
Reviewed-by: Michael Kriese <michael.kriese@gmx.de>
Co-authored-by: Renovate Bot <bot@kriese.eu>
Co-committed-by: Renovate Bot <bot@kriese.eu>

Update dependency webpack to v5.104.1 [SECURITY] (v14.0/forgejo) (#11398) ... 6b6e9da3cd

Reviewed-on: https://codeberg.org/forgejo/forgejo/pulls/11398
Reviewed-by: Gusted <gusted@noreply.codeberg.org>
Reviewed-by: Michael Kriese <michael.kriese@gmx.de>
Co-authored-by: Renovate Bot <bot@kriese.eu>
Co-committed-by: Renovate Bot <bot@kriese.eu>

[v14.0/forgejo] chore: bump go-git/v5 indirect dependency for govulncheck (#11412) ... f4f3a3e0f3

Unable to backport to v14 currently due to govulncheck ([example](https://codeberg.org/forgejo/forgejo/actions/runs/138106/jobs/11/attempt/2)).

#11396 was already opened and merged in v11, but v14 is currently blocked.

Reviewed-on: https://codeberg.org/forgejo/forgejo/pulls/11412
Reviewed-by: 0ko <0ko@noreply.codeberg.org>
Co-authored-by: Mathieu Fenniak <mathieu@fenniak.net>
Co-committed-by: Mathieu Fenniak <mathieu@fenniak.net>

[v14.0/forgejo] fix: cleanup of multi-platform container images (#11254) ... dbdbd0f5e6

**Backport:** https://codeberg.org/forgejo/forgejo/pulls/11246

This change fixes an issue that makes Forgejo clean up too many versions of a container package even though it should keep them according to the rules set for the package.

The issue affects multi-platform container images.
Forgejo adds a package version for each platform (for example `linux/amd64`, `linux/arm64`) in addition to the actual tag (for example `0.6.0` or `latest`).

This results in rows in the table `package_version` similar to this (unimportant columns omitted for brevity):

| **lower_version** | **created_unix** |
|---|---|
| `latest` | `1768742887`|
| `0.6.0` | `1768742886` |
| `sha256:038e...` | `1768742886` |
| `sha256:fc38...` | `1768742886` |
| `0.5.0` | `1768742864` |
| `sha256:806d...` | `1768742864` |
| `sha256:0a19...` | `1768742864` |
| `0.4.0` | `1768742848` |
| `...` | `...` |

The code assumes that the first `<keep count>` entries can be ignored and considers every entry after `<keep count>` as eligible for cleanup.
That doesn't work for multi-platform container images because, for `<keep count>=5`, it considers version `0.4.0` as eligible.

## Checklist

The [contributor guide](https://forgejo.org/docs/next/contributor/) contains information that will be helpful to first time contributors. There also are a few [conditions for merging Pull Requests in Forgejo repositories](https://codeberg.org/forgejo/governance/src/branch/main/PullRequestsAgreement.md). You are also welcome to join the [Forgejo development chatroom](https://matrix.to/#/#forgejo-development:matrix.org).

### Tests

- I added test coverage for Go changes...
  - [x] in their respective `*_test.go` for unit tests.
  - [ ] in the `tests/integration` directory if it involves interactions with a live Forgejo server.
- I added test coverage for JavaScript changes...
  - [ ] in `web_src/js/*.test.js` if it can be unit tested.
  - [ ] in `tests/e2e/*.test.e2e.js` if it requires interactions with a live Forgejo server (see also the [developer guide for JavaScript testing](https://codeberg.org/forgejo/forgejo/src/branch/forgejo/tests/e2e/README.md#end-to-end-tests)).

### Documentation

- [ ] I created a pull request [to the documentation](https://codeberg.org/forgejo/docs) to explain to Forgejo users how to use this change.
- [x] I did not document these changes and I do not expect someone else to do it.

### Release notes

- [x] This change will be noticed by a Forgejo user or admin (feature, bug fix, performance, etc.). I suggest to include a release note for this change.
- [ ] This change is not visible to a Forgejo user or admin (refactor, dependency upgrade, etc.). I think there is no need to add a release note for this change.

*The decision if the pull request will be shown in the release notes is up to the mergers / release team.*

The content of the `release-notes/<pull request number>.md` file will serve as the basis for the release notes. If the file does not exist, the title of the pull request will be used instead.

<!--start release-notes-assistant-->

## Release notes
<!--URL:https://codeberg.org/forgejo/forgejo-->
- Bug fixes
  - [PR](https://codeberg.org/forgejo/forgejo/pulls/11246): <!--number 11246 --><!--line 0 --><!--description Y2xlYW51cCBvZiBtdWx0aS1wbGF0Zm9ybSBjb250YWluZXIgaW1hZ2Vz-->cleanup of multi-platform container images<!--description-->
<!--end release-notes-assistant-->

Co-authored-by: wandhydrant <wandhydrant@noreply.codeberg.org>
Reviewed-on: https://codeberg.org/forgejo/forgejo/pulls/11254
Reviewed-by: Mathieu Fenniak <mfenniak@noreply.codeberg.org>
Co-authored-by: forgejo-backport-action <forgejo-backport-action@noreply.codeberg.org>
Co-committed-by: forgejo-backport-action <forgejo-backport-action@noreply.codeberg.org>

[v14.0/forgejo] ci: ensure correct node version (#11467) ... b72473d114

Backport of forgejo/forgejo!11280

- ensure we use the defined node version on ci, so renovate and ci use same version
- fix lockfile to match npm version
- add some debugging to ci

Reviewed-on: https://codeberg.org/forgejo/forgejo/pulls/11467
Reviewed-by: Mathieu Fenniak <mfenniak@noreply.codeberg.org>
Reviewed-by: 0ko <0ko@noreply.codeberg.org>
Co-authored-by: Gusted <postmaster@gusted.xyz>
Co-committed-by: Gusted <postmaster@gusted.xyz>

Update module code.superseriousbusiness.org/exif-terminator to v0.11.1 (v14.0/forgejo) (#11464) ... 456be57bb7

Reviewed-on: https://codeberg.org/forgejo/forgejo/pulls/11464
Reviewed-by: Gusted <gusted@noreply.codeberg.org>
Co-authored-by: Renovate Bot <bot@kriese.eu>
Co-committed-by: Renovate Bot <bot@kriese.eu>

Update dependency minimatch to v10.2.3 [SECURITY] (v14.0/forgejo) (#11415) ... aca1775dae

Reviewed-on: https://codeberg.org/forgejo/forgejo/pulls/11415
Reviewed-by: Gusted <gusted@noreply.codeberg.org>
Co-authored-by: Renovate Bot <bot@kriese.eu>
Co-committed-by: Renovate Bot <bot@kriese.eu>

Update https://data.forgejo.org/actions/setup-forgejo action to v3.1.7 (v14.0/forgejo) (#11475) ... d0dd0928be

Reviewed-on: https://codeberg.org/forgejo/forgejo/pulls/11475
Reviewed-by: Michael Kriese <michael.kriese@gmx.de>
Co-authored-by: Renovate Bot <bot@kriese.eu>
Co-committed-by: Renovate Bot <bot@kriese.eu>

Merge branch 'v14.0/forgejo' of https://codeberg.org/forgejo/forgejo into feat/granular-watch-settings-clean 6d6599d432

pat-s added 1 commit 2026-03-03 08:16:56 +00:00

upd license headers 047d4816bc

pat-s merged commit b54ffb340e into v14.0/forgejo-codefloe 2026-03-03 09:22:20 +00:00

pat-s deleted branch feat/granular-watch-settings-clean 2026-03-03 09:22:21 +00:00

pat-s referenced this pull request from a commit 2026-03-03 09:22:23 +00:00

feat: granular watch settings with event filtering and author exclusions (#21)

pat-s referenced this pull request from a commit 2026-06-01 14:54:55 +00:00

fix(ui): restore unified release-notification template body

pat-s referenced this pull request 2026-06-01 14:55:10 +00:00

fix(ui): restore unified release-notification template body #37

pat-s referenced this pull request from a commit 2026-06-01 16:03:27 +00:00

fix(ui): restore unified release-notification template body (#37)

Sign in to join this conversation.

Reviewers

No reviewers

Labels

Clear labels

  

bug

Something is not working

  

dashboard

Static dashboard

  

dependency 📦️

  

type

enhancement

Improve an existing feature/option

  

type

feature

New feature

  

type

question

Usage related question

  

type

refactor

Refactor existing code without a particular/direct improvement for users

No labels

bug

dashboard

dependency 📦️

type

enhancement

type

feature

type

question

type

refactor

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

2 participants

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

codefloe/forgejo-codefloe!21

No description provided.