Skip to content
Snippets Groups Projects

Add supported versions of GitLab to project and provider documentation

Points 1+2 from #6431 (closed)

Edited by 🤖 GitLab Bot 🤖

Merge request reports

Loading
Loading

Activity

Filter activity
  • Approvals
  • Assignees & reviewers
  • Comments (from bots)
  • Comments (from users)
  • Commits & branches
  • Edits
  • Labels
  • Lock status
  • Mentions
  • Merge request status
  • Tracking
  • Timo Furrer
  • Heidi Berry added 12 commits

    added 12 commits

    • e66061c7...4b807daf - 10 commits from branch gitlab-org:main
    • 67eafb24 - Merge branch 'main' into add-version-support-to-docs
    • f75c6d51 - Update draft policy following feedback

    Compare with previous version

  • Heidi Berry added 1 commit

    added 1 commit

    • 4a754179 - Update draft policy following feedback

    Compare with previous version

  • Timo Furrer changed milestone to %17.9

    changed milestone to %17.9

  • Timo Furrer approved this merge request

    approved this merge request

  • Timo Furrer resolved all threads

    resolved all threads

    • :wave: @timofurrer, thanks for approving this merge request.

      This is the first time the merge request has been approved. To ensure we don't only run predictive pipelines, and we don't break master, please start a new pipeline before merging.

      Please wait for the pipeline to start before resolving this discussion and set auto-merge for the new pipeline. See merging a merge request for more details.

  • Reviewer roulette

    Changes that require review have been detected! A merge request is normally reviewed by both a reviewer and a maintainer in its primary category and by a maintainer in all other categories.

    To spread load more evenly across eligible reviewers, Danger has picked a candidate for each review slot. Feel free to override these selections if you think someone else would be better-suited or use the GitLab Review Workload Dashboard to find other available reviewers.

    To read more on how to use the reviewer roulette, please take a look at the Engineering workflow and code review guidelines. Please consider assigning a reviewer or maintainer who is a domain expert in the area of the merge request.

    Once you've decided who will review this merge request, mention them as you normally would! Danger does not automatically notify them for you.

    Reviewer Maintainer
    @tigerwnz profile link current availability (UTC+13) @timofurrer profile link current availability (UTC+1)

    If needed, you can retry the :repeat: danger-review job that generated this comment.

    Generated by :no_entry_sign: Danger

  • Timo Furrer mentioned in commit 39f048e4

    mentioned in commit 39f048e4

  • merged

  • Hi @heidi.berry :wave:

    :tada: See where you rank! Check your spot on the contributor leaderboard and unlock rewards.


    How was your code review experience with this merge request? Please tell us how we can continue to iterate and improve:

    1. React with a :thumbsup: or a :thumbsdown: on this comment to describe your experience.
    2. Create a new comment starting with @gitlab-bot feedback below, and leave any additional feedback you have for us in the comment.

    As a benefit of being a GitLab Community Contributor, you have access to GitLab Duo, our AI-powered features. With Code Suggestions, Chat, Root Cause Analysis and more AI-powered features, GitLab Duo helps to boost your efficiency and effectiveness by reducing the time required to write and understand code and pipelines. Visit the GitLab Duo documentation to learn more about the benefits.

    Thanks for your help! :heart:

    This message was generated automatically. Improve it or delete it.

  • Loading
  • Loading
  • Loading
  • Loading
  • Loading
  • Loading
  • Loading
  • Loading
  • Loading
  • Loading
  • Please register or sign in to reply
    Loading