Re-write Workflow Linter in Go for better DX and distribution and extend config for 'trusted repos' #17290
aj0413
started this conversation in
Password Manager
Replies: 2 comments 1 reply
-
|
✨ Thank you for your code contribution proposal! While the Bitwarden team reviews your submission, we encourage you to check out our contribution guidelines. Please ensure that your code contribution includes a detailed description of what you would like to contribute, along with any relevant screenshots and links to existing feature requests. This information helps us gather feedback from the community and Bitwarden team members before you start writing code. To keep discussions focused, posts that do not include a proposal for a code contribution will be removed.
Thank you for contributing to Bitwarden! |
Beta Was this translation helpful? Give feedback.
0 replies
This comment was marked as off-topic.
This comment was marked as off-topic.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Select Topic Area
✅ Code Contribution Proposal
Code Contribution Proposal
Pretty much the title.
I've been using the workflow linter and like it a lot, but think it would better live as a Go CLI tool instead of Python; for all the same reasons other devops CLI tools are generally writen in Go
Additionally, I'd like to extend the functionality further by making the hardcoded trusted repo path 'bitwarden' into a config driven value
Not a huge fan of creating Linux N+1 problem if BW team has significant issues with this proposal, but would be open to me extending the current Python code base.
Beta Was this translation helpful? Give feedback.
All reactions