Searched refs:MRs (Results 1 – 8 of 8) sorted by relevance
55 std::vector<Record*> MRs = Records.getAllDerivedDefinitions("HwMode"); in CodeGenHwModes() local58 for (auto I = MRs.begin(), E = MRs.end(); I != E; ++I) { in CodeGenHwModes()61 MRs.erase(I); in CodeGenHwModes()65 for (Record *R : MRs) { in CodeGenHwModes()
8 We use it to test merge requests (MRs) before merging them (pre-merge testing),10 (this is necessary because we still allow commits to be pushed outside of MRs,33 If the GitLab CI doesn't seem to be running on your fork (or MRs, as they run100 turnaround time that we can get our MRs through marge-bot without the180 (forks inherit images from the main repo, but MRs don't propagate
79 Note that this token is visible to anybody that can submit MRs to
218 - Please send MRs from a personal fork rather than from the main Mesa
3675 - ci: Create test-docs job in mesa/mesa pipelines for MRs3676 - ci: Don't exclude "success" job from mesa/mesa pipelines for MRs3677 - ci: Restrict "success" job to pipelines for MRs
782 - docs: Add a note that MRs should still include any r-b or a-b tags.
1546 - gitlab-ci: limit the automatic CI to master and MRs
3498 - gitlab-ci: Only trigger test-docs job automatically for MRs