Print friendly error message on bad detected yaml #1578
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
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## main #1578 +/- ##
==========================================
+ Coverage 63.24% 63.78% +0.53%
==========================================
Files 139 140 +1
Lines 10778 10876 +98
==========================================
+ Hits 6817 6937 +120
+ Misses 3436 3409 -27
- Partials 525 530 +5 ☔ View full report in Codecov by Sentry. |
chmouel
force-pushed
the
print-friendly-error-message-on-bad-detected-yaml
branch
2 times, most recently
from
8a8a00d to
5ecf433
Compare
|
lgtm |
chmouel
force-pushed
the
print-friendly-error-message-on-bad-detected-yaml
branch
from
5ecf433 to
9a88078
Compare
|
Thanks @piyush-garg I have addedd a e2e test on ghe (since it's provider specific) in my latest push and reworded the resolver documentation along the way... diff of the changes https://github.com/openshift-pipelines/pipelines-as-code/compare/5ecf43355fcabad5e2666eeae490073163bd7bb0..53a3c18eb4757e3d1cc78a07c852246bac9b7196 |
We now print a more friendly error message when we detect a bad yaml by showing the errors on the git provider interface and the namespace events stream. Signed-off-by: Chmouel Boudjnah <chmouel@redhat.com>
chmouel
force-pushed
the
print-friendly-error-message-on-bad-detected-yaml
branch
from
16823e4 to
53a3c18
Compare
vdemeester
approved these changes
Feb 13, 2024
|
/lgtm |
7 tasks
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.
We now print a more friendly error message when we detect a bad yaml by showing the errors on the git provider interface and the namespace events stream.
support github/bitbucket/gitlab/gitea
this is how it looks like:
jira: https://issues.redhat.com/browse/SRVKP-4109
Changes
Submitter Checklist
📝 Please ensure your commit message is clear and informative. For guidance on crafting effective commit messages, refer to the How to write a git commit message guide. We prefer the commit message to be included in the PR body itself rather than a link to an external website (ie: Jira ticket).
♽ Before submitting a PR, run make test lint to avoid unnecessary CI processing. For an even more efficient workflow, consider installing pre-commit and running pre-commit install in the root of this repository.
✨ We use linters to maintain clean and consistent code. Please ensure you've run make lint before submitting a PR. Some linters offer a --fix mode, which can be executed with the command make fix-linters (ensure markdownlint and golangci-lint tools are installed first).
📖 If you're introducing a user-facing feature or changing existing behavior, please ensure it's properly documented.
🧪 While 100% coverage isn't a requirement, we encourage unit tests for any code changes where possible.
🎁 If feasible, please check if an end-to-end test can be added. See README for more details.
🔎 If there's any flakiness in the CI tests, don't necessarily ignore it. It's better to address the issue before merging, or provide a valid reason to bypass it if fixing isn't possible (e.g., token rate limitations).