Getting `changesNotSentForReview` Query Parameter Set to `true` While Releasing Android App from Appcenter.ms
Understanding `changesNotSentForReview`
The `changesNotSentForReview` query parameter in App Center is a vital setting that influences the release process of your Android app. It directly controls whether a new app release triggers a code review process.
* **`changesNotSentForReview=true`**: This setting bypasses the code review stage. Your app will be released directly, making it suitable for hotfixes, emergency updates, or minor changes.
* **`changesNotSentForReview=false`**: This is the default setting and activates the code review workflow. It allows your team to review changes before the app is released, promoting a collaborative and quality-focused approach.
Setting `changesNotSentForReview` to `true` During Release
You can modify the `changesNotSentForReview` parameter while releasing your Android app through App Center. Follow these steps:
1. **Log into App Center:** Access your App Center account and navigate to your Android app project.
2. **Release Creation:** Initiate a new release by selecting the **”Release”** button within your app’s dashboard.
3. **Release Notes:** Provide the necessary details for the release, such as version number, release notes, and any relevant information.
4. **Advanced Options:** Look for the “Advanced Options” section within the release creation flow.
5. **Query Parameters:** Locate the option to add query parameters.
6. **Set `changesNotSentForReview`:** Insert the following parameter: `changesNotSentForReview=true`
7. **Submit for Release:** Complete the remaining release process, and your app will be released without undergoing code review.
Table: Release Behaviors
| `changesNotSentForReview` | Code Review Triggered | Release Behavior |
|—|—|—|
| `true` | No | Direct Release |
| `false` | Yes | Code Review Required |
Example Scenario: Hotfix Release
Imagine you need to urgently address a critical bug in your app. You have a fix ready and need to release it immediately. In this case, setting `changesNotSentForReview` to `true` allows for a fast release cycle without the need for code review.
“`html
changesNotSentForReview=true
“`
Important Notes:
* **Responsible Use**: Use this option judiciously, as bypassing code review may introduce potential risks.
* **Team Communication**: Clearly communicate with your team if you’re releasing an update with `changesNotSentForReview=true` to ensure everyone is aware of the bypass.
* **Documentation**: Maintain accurate documentation for all releases, particularly when using `changesNotSentForReview=true`, to ensure transparency and track changes.
By understanding and utilizing the `changesNotSentForReview` query parameter, you can effectively control the release process of your Android app on App Center. This flexibility allows for swift releases when necessary while promoting a collaborative and quality-driven development approach through code review.