You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
#227 Is likely a pre-requisite to this enhancement.
For the purposes of auditing everything we are responsible for, I think the linter should be able to run across the entirety of aggregate recusively.
When we add new linter rules, we inherently cause new issues to crop-up across the feedstocks. It would be beneficial to detect and anticipate the fallout from adding new rules. It may also lend itself to better automated tooling in the future.
The text was updated successfully, but these errors were encountered:
This is possible with the anaconda-expeditor hackdays project. Would love to get that productionized either in the linter repo or somewhere else, and mentioned here.
We shouldn't rebuild a package just for the sake of making sure the linter doesn't throw errors.
Also, this will help find bugs within the linter itself.
#227 Is likely a pre-requisite to this enhancement.
For the purposes of auditing everything we are responsible for, I think the linter should be able to run across the entirety of
aggregate
recusively.When we add new linter rules, we inherently cause new issues to crop-up across the feedstocks. It would be beneficial to detect and anticipate the fallout from adding new rules. It may also lend itself to better automated tooling in the future.
The text was updated successfully, but these errors were encountered: