chore(cfnspec): fix the cfnspec update #25320
Merged
Conversation
This file contains 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
The cfnspec job currently doesn't create a PR anymore, because the validation is wrong, and fails the job that creates the PR. Do the additional "did types get renamed" validation only at build time in a PR, not in the job that creates the PR, so we get more visibility on the changes and it's easier to pick up the work to fix it.
|
|
mrgrain
approved these changes
Apr 26, 2023
|
Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
|
Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
|
Unfortunately this merge broke testing for all PRs that followed: |
|
Fixed by #25326 |
madeline-k
pushed a commit
that referenced
this pull request
Apr 27, 2023
The cfnspec job currently doesn't create a PR anymore, because the validation is wrong, and fails the job that creates the PR. Do the additional "did types get renamed" validation only at build time in a PR, not in the job that creates the PR, so we get more visibility on the changes and it's easier to pick up the work to fix it. ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
madeline-k
added a commit
that referenced
this pull request
Apr 27, 2023
This reverts commit 3fa9079.
corymhall
pushed a commit
that referenced
this pull request
May 9, 2023
The cfnspec job currently doesn't create a PR anymore, because the validation is wrong, and fails the job that creates the PR. Do the additional "did types get renamed" validation only at build time in a PR, not in the job that creates the PR, so we get more visibility on the changes and it's easier to pick up the work to fix it. ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
mergify bot
added a commit
that referenced
this pull request
May 9, 2023
chore(cfnspec): fix the cfnspec update (#25320)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The cfnspec job currently doesn't create a PR anymore, because the validation is wrong, and fails the job that creates the PR.
Do the additional "did types get renamed" validation only at build time in a PR, not in the job that creates the PR, so we get more visibility on the changes and it's easier to pick up the work to fix it.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license