Skip to content

Add a CI workflow to lint code #12

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

Merged
merged 1 commit into from
Nov 10, 2020
Merged

Add a CI workflow to lint code #12

merged 1 commit into from
Nov 10, 2020

Conversation

per1234
Copy link
Contributor

@per1234 per1234 commented Oct 30, 2020

No description provided.

@per1234 per1234 requested a review from silvanocerza October 30, 2020 05:29
@per1234 per1234 requested a review from a team November 10, 2020 10:45
@per1234 per1234 merged commit 6a25f07 into main Nov 10, 2020
@per1234 per1234 deleted the per1234/lint-workflow branch November 10, 2020 14:33
@per1234 per1234 added topic: infrastructure Related to project infrastructure type: enhancement Proposed improvement labels Sep 29, 2021
@per1234 per1234 self-assigned this Nov 20, 2021
per1234 added a commit to per1234/arduino-lint that referenced this pull request Oct 16, 2024
…" workflow

The digital certificates used for code signing are often stored in an archive file of the PKCS arduino#12 format, which allows
multiple objects to be bundled in a single file.

However, it also might occur that a single certificate is stored in X.509 format.

Previously, the "Check Certificates" workflow only supported certificates in a PKCS arduino#12 archive. Support is hereby added
to the workflow for validation of X.509 certificates in addition to PKCS arduino#12.
per1234 added a commit to per1234/arduino-lint that referenced this pull request Oct 16, 2024
…" workflow

The digital certificates used for code signing are often stored in an archive file of the PKCS arduino#12 format, which allows
multiple objects to be bundled in a single file.

However, it also might occur that a single certificate is stored in X.509 format.

Previously, the "Check Certificates" workflow only supported certificates in a PKCS arduino#12 archive. Support is hereby added
to the workflow for validation of X.509 certificates in addition to PKCS arduino#12.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
topic: infrastructure Related to project infrastructure type: enhancement Proposed improvement
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants