Create separate feature flag for require_organization for Project Model
-
Please check this box if this contribution uses AI-generated content (including content generated by GitLab Duo features) as outlined in the GitLab DCO & CLA. As a benefit of being a GitLab Community Contributor, you can request access to GitLab Duo.
What does this MR do and why?
References
Please include cross links to any resources that are relevant to this MR This will give reviewers and future readers helpful context to give an efficient review of the changes introduced.
MR acceptance checklist
Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.
Screenshots or screen recordings
Screenshots are required for UI changes, and strongly recommended for all other merge requests.
Before | After |
---|---|
How to set up and validate locally
Numbered steps to set up and validate the change are strongly suggested.
Related to #501257 (closed)
Merge request reports
Activity
added pipelinetier-1 label
Thanks for your contribution to GitLab @rutvikchandla3!
Did you know about our community forks? Working from there will make your contribution process easier. Please check it out!
- If you need help, page a coach by clicking here or come say hi on Discord.
- When you're ready, request a review by clicking here.
- We welcome AI-generated contributions and offer complimentary access to GitLab Duo! Check out the top of the merge request description to learn more about using AI while contributing.
- To add labels to your merge request, comment
@gitlab-bot label ~"label1" ~"label2"
.
This message was generated automatically. You're welcome to improve it.
added Community contribution workflowin dev labels
assigned to @rutvikchandla3
added linked-issue label
mentioned in issue #501257 (closed)
- Resolved by Rutvik Chandla
@rutvikchandla3 Thanks for picking this up! Highly appreciated!
It looks like it is ready for review. I will assign myself as reviewer and will have a look this week.
requested review from @rutgerwessels
- Resolved by Rutvik Chandla
- Resolved by Rutvik Chandla
@rutvikchandla3 Thanks for picking this up. I have two small change requests. Let me know when you applied them, then I can have another look.
requested review from @rutgerwessels
- Resolved by Abdul Wadood
@rutvikchandla3 Thanks for the changes. Looks good, approved!
requested review from @abdwdd
added pipeline:mr-approved label
added pipelinetier-3 pipeline:run-e2e-omnibus-once labels and removed pipelinetier-1 label
Before you set this MR to auto-merge
This merge request will progress on pipeline tiers until it reaches the last tier: pipelinetier-3.
Before you set this MR to auto-merge, please check the following:
- You are the last maintainer of this merge request
- The latest pipeline for this merge request is pipelinetier-3 (You can find which tier it is in the pipeline name)
- This pipeline is recent enough (created in the last 8 hours)
If all the criteria above apply, please set auto-merge for this merge request.
See pipeline tiers and merging a merge request for more details.
- A deleted user
added backend feature flag labels
1 Warning This merge request does not refer to an existing milestone. 1 Message CHANGELOG missing: If this merge request needs a changelog entry, add the
Changelog
trailer to the commit message you want to add to the changelog.If this merge request doesn't need a CHANGELOG entry, feel free to ignore this message.
Reviewer roulette
Category Reviewer Maintainer backend @SamWord
(UTC-4)
@ahmed.hemdan
(UTC+1)
Please refer to documentation page for guidance on how you can benefit from the Reviewer Roulette, or use the GitLab Review Workload Dashboard to find other available reviewers.
If needed, you can retry the
danger-review
job that generated this comment.Generated by
DangerE2E Test Result Summary
allure-report-publisher
generated test report!e2e-test-on-gdk:
test report for 8433dbdaexpand test summary
+------------------------------------------------------------------+ | suites summary | +-------------+--------+--------+---------+-------+-------+--------+ | | passed | failed | skipped | flaky | total | result | +-------------+--------+--------+---------+-------+-------+--------+ | Plan | 152 | 0 | 0 | 0 | 152 | ✅ | | Data Stores | 66 | 0 | 0 | 0 | 66 | ✅ | | Verify | 90 | 0 | 2 | 0 | 92 | ✅ | | Create | 244 | 0 | 4 | 0 | 248 | ✅ | | Govern | 146 | 0 | 6 | 2 | 152 | ✅ | | Monitor | 16 | 0 | 0 | 0 | 16 | ✅ | | Package | 34 | 0 | 0 | 0 | 34 | ✅ | | Release | 10 | 0 | 0 | 0 | 10 | ✅ | | Analytics | 4 | 0 | 0 | 0 | 4 | ✅ | | Fulfillment | 4 | 0 | 0 | 0 | 4 | ✅ | | Secure | 8 | 0 | 0 | 0 | 8 | ✅ | | Manage | 2 | 0 | 0 | 0 | 2 | ✅ | +-------------+--------+--------+---------+-------+-------+--------+ | Total | 776 | 0 | 12 | 2 | 788 | ✅ | +-------------+--------+--------+---------+-------+-------+--------+
e2e-test-on-cng:
test report for 8433dbdaexpand test summary
+------------------------------------------------------------------+ | suites summary | +-------------+--------+--------+---------+-------+-------+--------+ | | passed | failed | skipped | flaky | total | result | +-------------+--------+--------+---------+-------+-------+--------+ | Verify | 50 | 0 | 15 | 10 | 65 | ✅ | | Govern | 81 | 0 | 12 | 10 | 93 | ✅ | | Create | 139 | 0 | 21 | 21 | 160 | ✅ | | Plan | 86 | 0 | 8 | 14 | 94 | ✅ | | Growth | 0 | 0 | 2 | 0 | 2 | ➖ | | Package | 24 | 0 | 14 | 0 | 38 | ✅ | | Monitor | 8 | 0 | 12 | 0 | 20 | ✅ | | Data Stores | 33 | 0 | 10 | 1 | 43 | ✅ | | Release | 5 | 0 | 1 | 0 | 6 | ✅ | | Fulfillment | 2 | 0 | 7 | 0 | 9 | ✅ | | Secure | 1 | 0 | 6 | 0 | 7 | ✅ | | Manage | 1 | 0 | 9 | 0 | 10 | ✅ | | Ai-powered | 0 | 0 | 2 | 0 | 2 | ➖ | | Analytics | 2 | 0 | 0 | 0 | 2 | ✅ | | Configure | 0 | 0 | 3 | 0 | 3 | ➖ | | ModelOps | 0 | 0 | 1 | 0 | 1 | ➖ | +-------------+--------+--------+---------+-------+-------+--------+ | Total | 432 | 0 | 123 | 56 | 555 | ✅ | +-------------+--------+--------+---------+-------+-------+--------+
reset approvals from @abdwdd and @rutgerwessels by pushing to the branch
requested review from @rutgerwessels
requested review from @abdwdd
started a merge train
@rutvikchandla3, how was your code review experience with this merge request? Please tell us how we can continue to iterate and improve:
- React with a
or a on this comment to describe your experience. - 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 can request access to GitLab Duo. With Code Suggestions, Chat and more AI-powered features, GitLab Duo helps to boost your efficiency and effectiveness by reducing the time required to write and understand code. Visit the Duo access project to request a GitLab Duo license and learn more about the benefits of GitLab Duo.
Subscribe to the GitLab Community Newsletter for contributor-focused content and opportunities to level up.
Thanks for your help!
This message was generated automatically. You're welcome to improve it.
- React with a
mentioned in commit 2c444118
added workflowstaging-canary label and removed workflowin dev label
added workflowcanary label and removed workflowstaging-canary label
changed milestone to %17.6
added workflowstaging label and removed workflowcanary label
added workflowproduction label and removed workflowstaging label
added workflowpost-deploy-db-production label and removed workflowproduction label
mentioned in issue #501373 (closed)
added releasedcandidate label
added releasedpublished label and removed releasedcandidate label
added devopstenant scale grouporganizations labels and removed devopsdata stores grouptenant scale [DEPRECATED] labels