Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

where is example-pr-checks.yaml? #108

Closed
pacospace opened this issue Apr 26, 2021 · 6 comments
Closed

where is example-pr-checks.yaml? #108

pacospace opened this issue Apr 26, 2021 · 6 comments
Labels
kind/documentation Categorizes issue or PR as related to documentation. kind/question Categorizes issue or PR as a support question. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. sig/devops Categorizes an issue or PR as relevant to SIG DevOps. sig/pipelines Categorizes an issue or PR as relevant to SIG Pipelines (CI/CD)

Comments

@pacospace
Copy link

As contributor,

I would like to see example of PR check file mentioned in README.

See: https://github.com/AICoE/aicoe-ci/blob/master/docs/how-to-contribute.md#how-to-contribute
@goern
Copy link
Member

goern commented May 27, 2021

/kind question
/sig pipelines

@sesheta sesheta added kind/question Categorizes issue or PR as a support question. sig/pipelines Categorizes an issue or PR as relevant to SIG Pipelines (CI/CD) labels May 27, 2021
@sesheta
Copy link
Contributor

sesheta commented Oct 15, 2021

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@sesheta sesheta added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Oct 15, 2021
@harshad16 harshad16 added kind/documentation Categorizes issue or PR as related to documentation. lifecycle/active Indicates that an issue or PR is actively being worked on by a contributor. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. sig/devops Categorizes an issue or PR as relevant to SIG DevOps. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Oct 21, 2021
@harshad16
Copy link
Member

Thanks for the kind question
The example pr yaml is here: https://github.com/AICoE/aicoe-ci/blob/master/tasks/example-pr-checks.yaml
we will update the docs.

@harshad16
Copy link
Member

cc: @Gregory-Pereira

@sesheta
Copy link
Contributor

sesheta commented Jan 19, 2022

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@sesheta sesheta added lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. and removed lifecycle/active Indicates that an issue or PR is actively being worked on by a contributor. labels Jan 19, 2022
@harshad16
Copy link
Member

The overall doc requires updates.
This issue would take care of it: #162

/remove-lifecycle stale

@sesheta sesheta removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 17, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/documentation Categorizes issue or PR as related to documentation. kind/question Categorizes issue or PR as a support question. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. sig/devops Categorizes an issue or PR as relevant to SIG DevOps. sig/pipelines Categorizes an issue or PR as relevant to SIG Pipelines (CI/CD)
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@goern @harshad16 @pacospace @sesheta