You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A suggestion from @HowardBraham, we want to avoid running CI on this l10n_crowdin_action branch. @Gudahtt suggests that we keep the lint step to catch issues with localized messages.
Scenario
No response
Design
No response
Technical Details
No response
Threat Modeling Framework
No response
Acceptance Criteria
No response
Stakeholder review needed before the work gets merged
Engineering (needed in most cases)
Design
Product
QA (automation tests are required to pass before merging PRs but not all changes are covered by automation tests - please review if QA is needed beyond automation tests)
Security
Legal
Marketing
Management (please specify)
Other (please specify)
References
No response
The text was updated successfully, but these errors were encountered:
I think it would be easiest to implement the "just run the lint step" using GitHub Actions. You're going to encounter great complexities if you try to do it within CircleCI.
I made some changes that I documented in this PR comment: #25489 (comment)
I am not sure if this will already stop running CI on the l10n_crowdin_action branch, but it might. There does appear to be a PR though (#24889), so let's keep an eye on this.
What is this about?
A suggestion from @HowardBraham, we want to avoid running CI on this
l10n_crowdin_action
branch.@Gudahtt suggests that we keep the lint step to catch issues with localized messages.
Scenario
No response
Design
No response
Technical Details
No response
Threat Modeling Framework
No response
Acceptance Criteria
No response
Stakeholder review needed before the work gets merged
References
No response
The text was updated successfully, but these errors were encountered: