Tracking Linting Issues

[Dullaz]

I made a quick python program to make a markup list of files that have linting issues so we can track them a bit better.

A gist of the program can be found here

We could tick any boxes that have been taken by a contributor and strike them through when the pull request is complete?

Output (05/10/2020 14:42 GMT) updated according to #5831 :

• cli.go
• commands/actions.go
• commands/actions_use_codegen.go
• commands/completion.go
• commands/console.go
• commands/docs.go
• commands/help.go
• commands/init.go
• commands/migrate_create.go
• commands/migrate_squash.go
• commands/plugins.go
• commands/plugins_install.go
• commands/plugins_list.go
• commands/scripts_update_config_v2.go
• global_config.go
• integration_test/v1/seeds/seeds.go
• integration_test/v2/metadata.go
• integration_test/v2/seeds.go
• migrate/cmd/commands.go
• migrate/database/driver_test.go
• migrate/database/hasuradb/settings.go
• migrate/database/hasuradb/types.go
• migrate/database/hasuradb/types_test.go
• migrate/database/migration.go
• migrate/migrate.go
• migrate/migration.go
• migrate/source/file/file_test.go
• migrate/source/migration.go
• migrate/source/stub/stub_test.go
• migrate/source/testing/testing.go
• migrate/status.go
• migrate/util.go
• pkg/console/apiserver.go
• plugins/scanner.go
• seed/create.go
• update/update.go
• util/git.go
• util/viper.go
• util/zip.go