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.

Sign up for GitHub

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

Jump to bottom

Mention linting in section 4.3.1 #223

Closed
aarongable opened this issue Jun 21, 2024 · 0 comments · Fixed by #232
Closed

Mention linting in section 4.3.1 #223

aarongable opened this issue Jun 21, 2024 · 0 comments · Fixed by #232
Assignees
@aarongable
Milestone
Q3 2024

Comments

@aarongable
Copy link
Contributor

aarongable commented Jun 21, 2024 •
edited
Loading

Ballot SC-075 will update Section 4.3.1 to require linting. We already do linting. We should mention that we do linting.

Maybe remove or simplify the mention of pre-issuance linting in Section 8.7, to avoid duplication.
aarongable added a commit that referenced this issue Sep 26, 2024
@aarongable
Explicitly state that we do pre-issuance linting
9994e71 
Fixes #223
@aarongable aarongable self-assigned this Sep 26, 2024
@aarongable aarongable added this to the Q3 2024 milestone Sep 26, 2024
@aarongable aarongable mentioned this issue Sep 26, 2024
Merged
bdaehlie pushed a commit that referenced this issue Oct 18, 2024
@aarongable
Explicitly state that we do pre-issuance linting (#232)
c9bafa0 
Update Section 4.3.1 to mention our pre-issuance linting, which is now
required by the BRs. Also rephrase Section 8.7 to mention our
post-issuance (rather than pre-issuance) linting, in line with what that
section of the BRs cares about.

Fixes #223
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@aarongable aarongable

Labels
None yet
Projects
None yet
Milestone
Q3 2024
Development

Successfully merging a pull request may close this issue.

Explicitly state that we do pre-issuance linting letsencrypt/cp-cps
1 participant
@aarongable