Adopt good practices from the Automation CoP
ericzolf opened this issue · 4 comments
Description
The Automation Community of Practice within Red Hat has gathered and is maintaining a guide of automation good practices, to be used by Red Hatters, partners and customers as a reference.
We've started to integrate some of your guidelines and best practices, not all are "compatible", hence we can't say that we have all you'd like but perhaps you might want to re-think it (and we're open to discussion).
Anyway, we've started to analyze your documents in redhat-cop/automation-good-practices#2 and I've been asked to word them in a PR.
My suggestion, and question, is if you'd like to join the effort and embrace those more generic good practices?
Issues go stale after 90d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.
If this issue is safe to close now please do so with /close.
/lifecycle stale
Stale issues rot after 30d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.
If this issue is safe to close now please do so with /close.
/lifecycle rotten
/remove-lifecycle stale
Rotten issues close after 30d of inactivity.
Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.
/close
@openshift-bot: Closing this issue.
In response to this:
Rotten issues close after 30d of inactivity.
Reopen the issue by commenting
/reopen.
Mark the issue as fresh by commenting/remove-lifecycle rotten.
Exclude this issue from closing again by commenting/lifecycle frozen./close
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.