Automatic merge of gitlab-org/gitlab master

app/services/projects/alerting/notify_service.rb

@@ -36,7 +36,7 @@ module Projects
 
       override :alert_source
       def alert_source
-        alert.monitoring_tool || integration&.name || 'Generic Alert Endpoint'
+        super || integration&.name || 'Generic Alert Endpoint'
       end
 
       def active_integration?

app/services/system_notes/alert_management_service.rb

@@ -73,7 +73,7 @@ module SystemNotes
     #
     # Returns the created Note object
     def log_resolving_alert(monitoring_tool)
-      body = "logged a resolving alert from **#{monitoring_tool}**"
+      body = "logged a recovery alert from **#{monitoring_tool}**"
 
       create_note(NoteSummary.new(noteable, project, User.alert_bot, body, action: 'new_alert_added'))
     end

changelogs/unreleased/sy-system-note-recovery-alert-string-change.yml

+---
+title: Update resolving alert system notes to use term Recovery Alert
+merge_request: 58513
+author:
+type: changed

doc/user/packages/container_registry/index.md

@@ -35,7 +35,8 @@ You can view the Container Registry for a project or group.
 1. Go to your project or group.
 1. Go to **Packages & Registries > Container Registry**.
 
-You can search, sort, filter, and [delete](#delete-images-from-within-gitlab) containers on this page.
+You can search, sort, filter, and [delete](#delete-images-from-within-gitlab)
+containers on this page. You can share a filtered view by copying the URL from your browser.
 
 Only members of the project or group can access a private project's Container Registry.
 

doc/user/packages/package_registry/index.md

@@ -19,7 +19,8 @@ You can view packages for your project or group.
 1. Go to the project or group.
 1. Go to **Packages & Registries > Package Registry**.
 
-You can search, sort, and filter packages on this page.
+You can search, sort, and filter packages on this page. You can share your search results by copying
+and pasting the URL from your browser.
 
 You can also find helpful code snippets for configuring your package manager or installing a given package.
 

doc/user/project/merge_requests/reviewing_and_managing_merge_requests.md

@@ -145,7 +145,7 @@ To seamlessly navigate among commits in a merge request:
 1. Select a commit to open it in the single-commit view.
 1. Navigate through the commits by either:
 
-   - Selecting **Prev** and **Next** buttons right beneath the tab buttons.
+   - Selecting **Prev** and **Next** buttons below the tab buttons.
    - Using the <kbd>X</kbd> and <kbd>C</kbd> keyboard shortcuts.
 
 ![Merge requests commit navigation](img/commit_nav_v13_11.png)
@@ -268,7 +268,7 @@ the **Merge** button is colored red.
 
 When a merge request is merged, you can see the post-merge pipeline status of
 the branch the merge request was merged into. For example, when a merge request
-is merged into the `master` branch and then triggers a deployment to the staging
+is merged into the [default branch](../repository/branches/default.md) and then triggers a deployment to the staging
 environment.
 
 Ongoing deployments are shown, and the state (deploying or deployed)

spec/services/system_notes/alert_management_service_spec.rb

@@ -69,7 +69,7 @@ RSpec.describe ::SystemNotes::AlertManagementService do
     end
 
     it 'has the appropriate message' do
-      expect(subject.note).to eq('logged a resolving alert from **Some Service**')
+      expect(subject.note).to eq('logged a recovery alert from **Some Service**')
     end
   end
 end