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.

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

Setup linter and format checker #13

Open
1 of 2 tasks
jonasKjellerup opened this issue Oct 25, 2022 · 0 comments · May be fixed by #71
Open
1 of 2 tasks

Setup linter and format checker #13

jonasKjellerup opened this issue Oct 25, 2022 · 0 comments · May be fixed by #71
Labels
a-meta Area: meta information, organisational changes, repository changes, etc. c-workflow Category: workflow changes d-easy Difficulty: easy - Good for newcomers facking An issue that should be solveable during a facking event p-low Priority: low

Comments

@jonasKjellerup
Copy link
Collaborator

jonasKjellerup commented Oct 25, 2022

To better enforce code standards, we should setup a linter configuration that can be used locally as well as for automated checks on merge requests.

  • Linter configuration
  • Github action
@jonasKjellerup jonasKjellerup added d-easy Difficulty: easy - Good for newcomers a-meta Area: meta information, organisational changes, repository changes, etc. p-low Priority: low c-workflow Category: workflow changes labels Oct 25, 2022
@jonasKjellerup jonasKjellerup moved this to New in F-Appen Oct 25, 2022
@jonasKjellerup jonasKjellerup moved this from New to Todo in F-Appen Oct 26, 2022
@krestenlaust krestenlaust added the facking An issue that should be solveable during a facking event label Oct 14, 2023
krestenlaust added a commit that referenced this issue Mar 7, 2024
Attempts to resolve #13
@krestenlaust krestenlaust linked a pull request Mar 7, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
a-meta Area: meta information, organisational changes, repository changes, etc. c-workflow Category: workflow changes d-easy Difficulty: easy - Good for newcomers facking An issue that should be solveable during a facking event p-low Priority: low
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants