Advanced auto merge
You can give the bot commands to customize how the bot assists you with merging your pull request when all merge policies pass.
To customize the auto-merge parameters, @ mention the bot (e.g. @msft-fluent-ui-bot
, @msft-github-bot
or @msftbot
depending on the bot identity providing auto-merge capabilities) and provide your instruction in English. Note that for all scenarios below, pre-configured merge policies at the GitHub level must still be satisfied (i.e. the bot will never bypass merge policies for you). Note that you must be a contributor - the bot will ignore all commands given by non-contributors.
At this time, the bot supports the following scenarios:
Examples of what to say (illustrative, not prescriptive nor exhaustive):
-
Only merge this pull request if it has 2 approvals.
-
require 3 sign offs.
-
Please make sure there are at least two approving reviews.
Examples of what to say (illustrative, not prescriptive nor exhaustive):
-
make sure @cliffkoh has a chance to review before you merge
-
do not merge unless @cliffkoh approves.
Examples of what to say (illustrative, not prescriptive nor exhaustive):
-
require sign-offs from @kkjeer and @JasonGore
-
hold this pr until all of the following approve: @kkjeer, @JasonGore, @dzearing
Examples of what to say (illustrative, not prescriptive nor exhaustive):
-
make sure @kkjeer, @dzearing or @JasonGore gets to approve
-
require approvals from any one of the following: @kkjeer, @JasonGore, @dzearing
Changing the time the pull-request is held open before the bot merges the pull request on your behalf
Examples of what to say (illustrative, not prescriptive nor exhaustive):
-
hold this pr for the next 2 hours
-
please wait 1 more day before merging this
-
delay merging this pull request for 2 hours 30 mins
Note that the examples above of what to say are only meant to be illustrative and not definitive.
Additionally, if the bot has misinterpreted you or you have changed your mind, you can express such an intent with a phrase like "nevermind" or "forget what I just told you".
on April 18th 2023 auto-merge.config.enforce
started to block all PR's (it never ran/finish).
As we use github automerge funcionatity anyways we removed it from required status checks to unblock contributors and use github build-in features.
Enforcement of auto-merge comments is handled by the auto-merge.config.enforce
status check. It's intended to run for each PR and automatically succeed if no AutoMerge policies apply. If this stops working, contact the bot team (check internal wiki for contact info).
- FAQ - Fabric and Stardust to Fluent UI
-
@fluentui/react
Version 9 -
@fluentui/react
Version 8 - Contributing to the
7.0
branch - How to apply themes (version 7/8)
- Planning and development process (for work by the core team)
- Conducting meetings Style guide
- Keeping up with review requests
- RFC review process
- Setup (configuring your environment)
- Fluent UI React version 7/8
- CLA
- Overview
- Repo structure
- Development process
- Contributing to previous versions
- API Extractor
- Build command changes made in early 2020
- Component implementation guide
- Creating a component
- Implementation Best Practices
- Theming
- Documenting
- Styling (old approach)
- Overview
- Testing with Jest
- E2E testing (Cypress)
- Visual testing (Screener)
- Accessibility review checklist