Prototype markdown table import into Github issues #203
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
❌ Deploy Preview for scrc-coding-guidelines failed.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Caution
BE VERY CAREFUL WHEN TRYING THIS SCRIPT: ONLY USE WITH DEDICATED TESTING REPOSITORIES FOR NOW. IT WILL WREAK HAVOC ON YOUR ISSUES!
This is an experiment to import coding rules from markdown tables. The approach works well, but the output format for the issues is not correct yet. The input format is also somewhat arbitrary at the moment and no filtering is done.
@PLeVasseur let me know what you think.
We could also use this to deal with #197, if we implement the reverse: Get a list of (properly tagged) issues and generate markdown / HTML from it. If we deploy this on Github pages (say, nightly), we'd have an always current list of rules and their respective state.