Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(ci): Change approach in listing the changed boards #10495

Merged
merged 1 commit into from
Oct 21, 2024

Conversation

P-R-O-C-H-Y
Copy link
Member

Description of Change

Changed the way to get the modified lines in boards to make the script work for PRs with more changes to boards.txt file, as the "Patch" in json is missing if there is a lot of lines changed.

Tests scenarios

Tested script locally.

Related links

Copy link
Contributor

github-actions bot commented Oct 21, 2024

Messages
📖 🎉 Good Job! All checks are passing!

👋 Hello P-R-O-C-H-Y, we appreciate your contribution to this project!


Click to see more instructions ...


This automated output is generated by the PR linter DangerJS, which checks if your Pull Request meets the project's requirements and helps you fix potential issues.

DangerJS is triggered with each push event to a Pull Request and modify the contents of this comment.

Please consider the following:
- Danger mainly focuses on the PR structure and formatting and can't understand the meaning behind your code or changes.
- Danger is not a substitute for human code reviews; it's still important to request a code review from your colleagues.
- To manually retry these Danger checks, please navigate to the Actions tab and re-run last Danger workflow.

Review and merge process you can expect ...


We do welcome contributions in the form of bug reports, feature requests and pull requests.

1. An internal issue has been created for the PR, we assign it to the relevant engineer.
2. They review the PR and either approve it or ask you for changes or clarifications.
3. Once the GitHub PR is approved we do the final review, collect approvals from core owners and make sure all the automated tests are passing.
- At this point we may do some adjustments to the proposed change, or extend it by adding tests or documentation.
4. If the change is approved and passes the tests it is merged into the default branch.

Generated by 🚫 dangerJS against 25b7a80

@me-no-dev me-no-dev added the Status: Pending Merge Pull Request is ready to be merged label Oct 21, 2024
@me-no-dev me-no-dev merged commit e509d33 into espressif:master Oct 21, 2024
11 checks passed
@P-R-O-C-H-Y P-R-O-C-H-Y changed the title fix(ci): Chnage approach in listing the changed boards fix(ci): Change approach in listing the changed boards Oct 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Pending Merge Pull Request is ready to be merged Type: CI & Testing
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants