De-linting is a time-consuming process. The aim of LINTY is to support an iterative process to clear out lint. It uses a configuration file which lists packages that currently contain lint, and ensures that:
packages listed in the configuration are removed once they are free of lint
packages not listed in the configuration continue to be free of lint
If either of the above statements is FALSE, LINTY prints out a warning and exits. If both statements are TRUE, LINTY prints out a table of lint counts for the packages that are listed in its configuration.
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.
## 📋 Pull Request Information
**Original PR:** https://github.com/sdras/awesome-actions/pull/165
**Author:** [@ArangoGutierrez](https://github.com/ArangoGutierrez)
**Created:** 8/29/2019
**Status:** ✅ Merged
**Merged:** 8/29/2019
**Merged by:** [@gep13](https://github.com/gep13)
**Base:** `master` ← **Head:** `patch-1`
---
### 📝 Commits (1)
- [`877208a`](https://github.com/sdras/awesome-actions/commit/877208a28f3d804f1e81afad0b0055cbe2b8d38c) Add GoLinty
### 📊 Changes
**1 file changed** (+1 additions, -0 deletions)
<details>
<summary>View changed files</summary>
📝 `README.md` (+1 -0)
</details>
### 📄 Description
https://github.com/marketplace/actions/go-linty
GitHub action to run Go lint checks on PR event
De-linting is a time-consuming process. The aim of LINTY is to support an iterative process to clear out lint. It uses a configuration file which lists packages that currently contain lint, and ensures that:
packages listed in the configuration are removed once they are free of lint
packages not listed in the configuration continue to be free of lint
If either of the above statements is FALSE, LINTY prints out a warning and exits. If both statements are TRUE, LINTY prints out a table of lint counts for the packages that are listed in its configuration.
---
<sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
📋 Pull Request Information
Original PR: https://github.com/sdras/awesome-actions/pull/165
Author: @ArangoGutierrez
Created: 8/29/2019
Status: ✅ Merged
Merged: 8/29/2019
Merged by: @gep13
Base:
master← Head:patch-1📝 Commits (1)
877208aAdd GoLinty📊 Changes
1 file changed (+1 additions, -0 deletions)
View changed files
📝
README.md(+1 -0)📄 Description
https://github.com/marketplace/actions/go-linty
GitHub action to run Go lint checks on PR event
De-linting is a time-consuming process. The aim of LINTY is to support an iterative process to clear out lint. It uses a configuration file which lists packages that currently contain lint, and ensures that:
packages listed in the configuration are removed once they are free of lint
packages not listed in the configuration continue to be free of lint
If either of the above statements is FALSE, LINTY prints out a warning and exits. If both statements are TRUE, LINTY prints out a table of lint counts for the packages that are listed in its configuration.
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.