Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Script] Release helper #25122

Merged
merged 120 commits into from
Jul 13, 2022
Merged

[Script] Release helper #25122

merged 120 commits into from
Jul 13, 2022

Conversation

BigCat20196
Copy link
Contributor

@BigCat20196 BigCat20196 commented Jul 7, 2022

@check-enforcer
Copy link

check-enforcer bot commented Jul 7, 2022

This pull request is protected by Check Enforcer.

What is Check Enforcer?

Check Enforcer helps ensure all pull requests are covered by at least one check-run (typically an Azure Pipeline). When all check-runs associated with this pull request pass then Check Enforcer itself will pass.

Why am I getting this message?

You are getting this message because Check Enforcer did not detect any check-runs being associated with this pull request within five minutes. This may indicate that your pull request is not covered by any pipelines and so Check Enforcer is correctly blocking the pull request being merged.

What should I do now?

If the check-enforcer check-run is not passing and all other check-runs associated with this PR are passing (excluding license-cla) then you could try telling Check Enforcer to evaluate your pull request again. You can do this by adding a comment to this pull request as follows:
/check-enforcer evaluate
Typically evaulation only takes a few seconds. If you know that your pull request is not covered by a pipeline and this is expected you can override Check Enforcer using the following command:
/check-enforcer override
Note that using the override command triggers alerts so that follow-up investigations can occur (PRs still need to be approved as normal).

What if I am onboarding a new service?

Often, new services do not have validation pipelines associated with them, in order to bootstrap pipelines for a new service, you can issue the following command as a pull request comment:
/azp run prepare-pipelines
This will run a pipeline that analyzes the source tree and creates the pipelines necessary to build and validate your pull request. Once the pipeline has been created you can trigger the pipeline using the following comment:
/azp run python - [service] - ci

@BigCat20196 BigCat20196 marked this pull request as ready for review July 13, 2022 01:51
@msyyc
Copy link
Member

msyyc commented Jul 13, 2022

/check-enforcer override

@msyyc msyyc merged commit ceb8d15 into Azure:main Jul 13, 2022
jeremydvoss pushed a commit to jeremydvoss/azure-sdk-for-python that referenced this pull request Jul 21, 2022
* update for Go

* check tag consistency and optize reply

* add write.md

* update go js readme

* update

* Update common.py

* Update common.py

* update assignee for JS

* update

* update

* Update common.py

* Update common.py

* Update release_helper.yml for Azure Pipelines

* Update common.py

* update

* Update common.py

* Update common.py

* Update main.py

* update

* update bot advice

* update

* update

* update excel

* update output function

* add exception handle for bad credential

* fix static varaible in class

* update auto_assignee algorithm

* update bot token to have a try

* update bot token

* force to single process

* test

* test

* test

* test

* fix bug

* fix

* update release_helper/js

* update release_helper/js

* fix bug

* update release helper

* Update js.py

* Update js.py

* Update js.py

* urldecode

* format

* add python

* fix

* add package name

* update package name

* update package name

* fix bug

* update get edit_content

* auto-close

* record release

* debug

* debug

* debug

* override run

* init readme link

* fix

* fix

* fix

* update assignee_token and auto-close

* fix

* debug

* fix

* auto-reply

* fix

* debug

* fix

* debug

* debug

* fix

* debugg

* update yaml

* change to add_label

* format

* add attention policy and remind policy

* add duplicated policy

* delete uesless code

* Update scripts/release_helper/utils.py

Co-authored-by: Yuchao Yan <[email protected]>

* update

* fix dependence version

* fix dependence version

* fix env

* update js assignee

* update js assignee

* fix find pr number bug

* update assignee logic

* debug

* debug

* update python assignee

* Update python.py

* debug

* debug

* delete useless code

* Update scripts/release_helper/python.py

Co-authored-by: Yuchao Yan <[email protected]>

* add multi api policy

* add tag inconsystency

* add specified tag

* Update scripts/release_helper/python.py

Co-authored-by: Yuchao Yan <[email protected]>

* update

* update multiapi policy

Co-authored-by: msyyc <[email protected]>
Co-authored-by: Zed <[email protected]>
Co-authored-by: Yiming Lei <[email protected]>
Co-authored-by: Yuchao Yan <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants