Fix output to outputs typos in ci.yaml everywhere #30490
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
(Facepalm) The typo of output -> outputs from apache#30482 was also in the ci.yaml where it was used and it was missed in this PR. I can blame the GitHub Actions stupid choice of accepting typoed names of outputs and replacing them with blank strings (which I raised as an issue a long time ago)
vincbeck
approved these changes
Apr 5, 2023
Member
Author
|
OK. Now it finally IS fixed
Comparing to:
|
jedcunningham
approved these changes
Apr 5, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
(Facepalm) The typo of output -> outputs from #30482 was also in the ci.yaml where it was used and it was missed in this PR.
I can blame the GitHub Actions stupid choice of accepting typoed names of outputs and replacing them with blank strings (which I raised as an issue a long time ago)
^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named
{pr_number}.significant.rstor{issue_number}.significant.rst, in newsfragments.