#810 fix: commit linter running on generated messages Pull request opened by FrankFlitton TL;DR Commit linter was running on auto-generated content with long URLs to github artifacts, triggering the lines longer than 100 chars rule. Type ☑︎ Bug Fix ☐ Feature ☐ Plugin Are all requirements met? ☑︎ Code completed ☑︎ Smoke tested ☐ Unit tests added ☐ Code documentation added ☐ Any pending items have an associated Issue Complete description • Made sure CI env variable was set - same as linter stage - that it was bypassing. • Added

[skip ci]

rule to the generated commit message which is recommended by semantic-release if running within a CI so you can avoid duplicate builds from change log diffs. • Remote pipeline is incrementally more in common with local dev environment. Follow-up issue NA flyteorg/flyteconsole GitHub Actions: Build & Push FlyteConsole Image GitHub Actions: Get Release Tag GitHub Actions: Generate Release ✅ 6 other checks have passed 6/9 successful checks

#810 fix: commit linter running on generated messages Pull request ready for review by FrankFlitton flyteorg/flyteconsole