amoghrajesh opened a new pull request, #44207:
URL: https://github.com/apache/airflow/pull/44207
<!--
Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements. See the NOTICE file
distributed with this work for additional information
regarding copyright ownership. The ASF licenses this file
to you under the Apache License, Version 2.0 (the
"License"); you may not use this file except in compliance
with the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing,
software distributed under the License is distributed on an
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
KIND, either express or implied. See the License for the
specific language governing permissions and limitations
under the License.
-->
<!--
Thank you for contributing! Please make sure that your code changes
are covered with tests. And in case of new features or big changes
remember to adjust the documentation.
Feel free to ping committers for the review!
In case of an existing issue, reference it using one of the following:
closes: #ISSUE
related: #ISSUE
How to write a good git commit message:
http://chris.beams.io/posts/git-commit/
-->
@eladkal found an edge case where if any provider doesn't have a changelog
to process, the process of `breeze release-management
generate-issue-content-providers` exits and doesn't continue ahead.
How was this tested?
1. Cleared the changelog entirely for `standard` provider to ensure it has
no PRs to process
2. Ran the `breeze release-management generate-issue-content-providers`
command before changes:
```
Skipping extracting PRs for provider qdrant as it is missing in dist
Skipping extracting PRs for provider redis as it is missing in dist
Skipping extracting PRs for provider salesforce as it is missing in dist
Skipping extracting PRs for provider samba as it is missing in dist
Skipping extracting PRs for provider segment as it is missing in dist
Skipping extracting PRs for provider sendgrid as it is missing in dist
Skipping extracting PRs for provider sftp as it is missing in dist
Skipping extracting PRs for provider singularity as it is missing in dist
Extracting PRs for provider slack
Extracting PRs for provider smtp
Extracting PRs for provider snowflake
Extracting PRs for provider sqlite
Skipping extracting PRs for provider ssh as it is missing in dist
Extracting PRs for provider standard
Skipping provider standard. The changelog file doesn't contain any PRs for
the release.
```
3. Ran the same command after the changes:
```
Extracting PRs for provider smtp
Extracting PRs for provider snowflake
Extracting PRs for provider sqlite
Extracting PRs for provider ssh
Extracting PRs for provider standard
I AM HERE for standard
Skipping provider standard. The changelog file doesn't contain any PRs for
the release.
Extracting PRs for provider tableau
Extracting PRs for provider telegram
Extracting PRs for provider teradata
Extracting PRs for provider trino
Extracting PRs for provider vertica
Extracting PRs for provider weaviate
Extracting PRs for provider yandex
```
<!-- Please keep an empty line above the dashes. -->
---
**^ Add meaningful description above**
Read the **[Pull Request
Guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#pull-request-guidelines)**
for more information.
In case of fundamental code changes, an Airflow Improvement Proposal
([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvement+Proposals))
is needed.
In case of a new dependency, check compliance with the [ASF 3rd Party
License Policy](https://www.apache.org/legal/resolved.html#category-x).
In case of backwards incompatible changes please leave a note in a
newsfragment file, named `{pr_number}.significant.rst` or
`{issue_number}.significant.rst`, in
[newsfragments](https://github.com/apache/airflow/tree/main/newsfragments).
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
