Check for existing open PRs before creating rc tag (DataDog#22254)

* Check for existing open PRs before creating rc tag

* lint

* better prompt

* changelog

* mute message

* silence atexit

* delete env vars that are set

* tests

* feedbacks

* remove test

* feedbac

* fix test

* don't care about auth

* formatting

* lint

* Update dependency resolution

---------

Co-authored-by: dd-agent-integrations-bot[bot] <dd-agent-integrations-bot[bot]@users.noreply.github.com> 9e1d7fc

Author: pull[bot]

ddev/cli/index.html

@@ -129,7 +129,7 @@
 </code></pre></div> <p><strong>Options:</strong></p> <table> <thead> <tr> <th>Name</th> <th>Type</th> <th>Description</th> <th>Default</th> </tr> </thead> <tbody> <tr> <td><code>--since</code></td> <td>text</td> <td>Initial Agent version</td> <td><code>6.3.0</code></td> </tr> <tr> <td><code>--to</code></td> <td>text</td> <td>Final Agent version</td> <td>None</td> </tr> <tr> <td><code>--write</code>, <code>-w</code></td> <td>boolean</td> <td>Write to the changelog file, if omitted contents will be printed to stdout</td> <td><code>False</code></td> </tr> <tr> <td><code>--help</code></td> <td>boolean</td> <td>Show this message and exit.</td> <td><code>False</code></td> </tr> </tbody> </table> <h3 id=ddev-release-branch>ddev release branch<a class=headerlink href=#ddev-release-branch title="Permanent link">&para;</a></h3> <p>Manage Agent release branches.</p> <p><strong>Usage:</strong></p> <div class=highlight><pre><span></span><code>ddev release branch [OPTIONS] COMMAND [ARGS]...
 </code></pre></div> <p><strong>Options:</strong></p> <table> <thead> <tr> <th>Name</th> <th>Type</th> <th>Description</th> <th>Default</th> </tr> </thead> <tbody> <tr> <td><code>--help</code></td> <td>boolean</td> <td>Show this message and exit.</td> <td><code>False</code></td> </tr> </tbody> </table> <h4 id=ddev-release-branch-create>ddev release branch create<a class=headerlink href=#ddev-release-branch-create title="Permanent link">&para;</a></h4> <p>Create a branch for a release of the Agent.</p> <p>BRANCH_NAME should match this pattern: ^\d+.\d+.x$<code>, for example</code>7.52.x`.</p> <p>If BRANCH_NAME is not provided, the command will suggest the next version based on existing branches.</p> <p>This command will also create the <code>backport/&lt;BRANCH_NAME&gt;</code> label in GitHub for this release branch.</p> <p><strong>Usage:</strong></p> <div class=highlight><pre><span></span><code>ddev release branch create [OPTIONS] [BRANCH_NAME]
 </code></pre></div> <p><strong>Options:</strong></p> <table> <thead> <tr> <th>Name</th> <th>Type</th> <th>Description</th> <th>Default</th> </tr> </thead> <tbody> <tr> <td><code>--help</code></td> <td>boolean</td> <td>Show this message and exit.</td> <td><code>False</code></td> </tr> </tbody> </table> <h4 id=ddev-release-branch-tag>ddev release branch tag<a class=headerlink href=#ddev-release-branch-tag title="Permanent link">&para;</a></h4> <p>Tag the release branch either as release candidate or final release.</p> <p><strong>Usage:</strong></p> <div class=highlight><pre><span></span><code>ddev release branch tag [OPTIONS]
-</code></pre></div> <p><strong>Options:</strong></p> <table> <thead> <tr> <th>Name</th> <th>Type</th> <th>Description</th> <th>Default</th> </tr> </thead> <tbody> <tr> <td><code>--final</code> / <code>--rc</code></td> <td>boolean</td> <td>Whether we're tagging the final release or a release candidate (rc).</td> <td><code>False</code></td> </tr> <tr> <td><code>--help</code></td> <td>boolean</td> <td>Show this message and exit.</td> <td><code>False</code></td> </tr> </tbody> </table> <h3 id=ddev-release-build>ddev release build<a class=headerlink href=#ddev-release-build title="Permanent link">&para;</a></h3> <p>Build a wheel for a check as it is on the repo HEAD</p> <p><strong>Usage:</strong></p> <div class=highlight><pre><span></span><code>ddev release build [OPTIONS] CHECK
+</code></pre></div> <p><strong>Options:</strong></p> <table> <thead> <tr> <th>Name</th> <th>Type</th> <th>Description</th> <th>Default</th> </tr> </thead> <tbody> <tr> <td><code>--final</code> / <code>--rc</code></td> <td>boolean</td> <td>Whether we're tagging the final release or a release candidate (rc).</td> <td><code>False</code></td> </tr> <tr> <td><code>--skip-open-pr-check</code></td> <td>boolean</td> <td>Skip checking GitHub for open PRs targeting this release branch before tagging.</td> <td><code>False</code></td> </tr> <tr> <td><code>--help</code></td> <td>boolean</td> <td>Show this message and exit.</td> <td><code>False</code></td> </tr> </tbody> </table> <h3 id=ddev-release-build>ddev release build<a class=headerlink href=#ddev-release-build title="Permanent link">&para;</a></h3> <p>Build a wheel for a check as it is on the repo HEAD</p> <p><strong>Usage:</strong></p> <div class=highlight><pre><span></span><code>ddev release build [OPTIONS] CHECK
 </code></pre></div> <p><strong>Options:</strong></p> <table> <thead> <tr> <th>Name</th> <th>Type</th> <th>Description</th> <th>Default</th> </tr> </thead> <tbody> <tr> <td><code>--sdist</code>, <code>-s</code></td> <td>boolean</td> <td>N/A</td> <td><code>False</code></td> </tr> <tr> <td><code>--help</code></td> <td>boolean</td> <td>Show this message and exit.</td> <td><code>False</code></td> </tr> </tbody> </table> <h3 id=ddev-release-changelog>ddev release changelog<a class=headerlink href=#ddev-release-changelog title="Permanent link">&para;</a></h3> <p>Manage changelogs.</p> <p><strong>Usage:</strong></p> <div class=highlight><pre><span></span><code>ddev release changelog [OPTIONS] COMMAND [ARGS]...
 </code></pre></div> <p><strong>Options:</strong></p> <table> <thead> <tr> <th>Name</th> <th>Type</th> <th>Description</th> <th>Default</th> </tr> </thead> <tbody> <tr> <td><code>--help</code></td> <td>boolean</td> <td>Show this message and exit.</td> <td><code>False</code></td> </tr> </tbody> </table> <h4 id=ddev-release-changelog-fix>ddev release changelog fix<a class=headerlink href=#ddev-release-changelog-fix title="Permanent link">&para;</a></h4> <p>Fix changelog entries.</p> <p>This command is only needed if you are manually writing to the changelog. For instance for marketplace and extras integrations. Don't use this in integrations-core because the changelogs there are generated automatically.</p> <p>The first line of every new changelog entry must include the PR number in which the change occurred. This command will apply this suffix to manually added entries if it is missing.</p> <p><strong>Usage:</strong></p> <div class=highlight><pre><span></span><code>ddev release changelog fix [OPTIONS]
 </code></pre></div> <p><strong>Options:</strong></p> <table> <thead> <tr> <th>Name</th> <th>Type</th> <th>Description</th> <th>Default</th> </tr> </thead> <tbody> <tr> <td><code>--help</code></td> <td>boolean</td> <td>Show this message and exit.</td> <td><code>False</code></td> </tr> </tbody> </table> <h4 id=ddev-release-changelog-new>ddev release changelog new<a class=headerlink href=#ddev-release-changelog-new title="Permanent link">&para;</a></h4> <p>This creates new changelog entries in Markdown format.</p> <p>If the ENTRY_TYPE is not specified, you will be prompted.</p> <p>The <code>--message</code> option can be used to specify the changelog text. If this is not supplied, an editor will be opened for you to manually write the entry. The changelog text that is opened defaults to the PR title, followed by the most recent commit subject. If that is sufficient, then you may close the editor tab immediately.</p> <p>By default, changelog entries will be created for all integrations that have changed code. To create entries only for specific targets, you may pass them as additional arguments after the entry type.</p> <p><strong>Usage:</strong></p> <div class=highlight><pre><span></span><code>ddev release changelog new [OPTIONS] [ENTRY_TYPE] [TARGETS]...