Open fivetran-catfritz opened 3 months ago
@fivetran-catfritz thanks for addressing all of my comments and helping inform me on the nature of the GitHub bot. Lastly, do you know if this automation starts tracking days after it's been implemented, or does it retroactively count the days? For example when we add this bot to a repo will it mark an existing issue from 2 years ago as stale? If so, we should probably do an audit of issues on each repo before releasing this action to ensure we are pinning issues that should be.
I like using the pinned label, but let's make sure we add it to each repo and include a description of the label. We can address this during the mass package update.
@fivetran-joemarkiewicz When the action runs each day, it looks at the "updated_at" field for the issue to determine staleness (this section of their readme explains it also), so yes for each repo it should mark existing issues. For example, it marked this test issue from 2 years ago as stale and closed.
And sounds good re the pinned labels!
Add a bot to manage staleness of issue and prs.
18