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.

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

Flakes test reporter supports reporting github issue in different org #2406

Open
chaodaiG opened this issue Sep 3, 2020 · 3 comments
Open
Labels
kind/enhancement lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.

Comments

@chaodaiG
Copy link
Contributor

chaodaiG commented Sep 3, 2020

Flakes test report currently only supports reporting github issues in the same repo where the test takes place, as configured in this yaml. As requested on https://knative.slack.com/archives/CCSNR4FCH/p1599021716069900, it's desired to report jobs from orgA as issues on orgB, for example, knative/serving tests create issues in knative-sandbox/net-{} repos

@chaodaiG
Copy link
Contributor Author

chaodaiG commented Sep 3, 2020

/kind enhancement

@github-actions
Copy link

github-actions bot commented Dec 2, 2020

This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen.Mark the issue as
fresh by adding the comment /remove-lifecycle stale.

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 2, 2020
@chizhg
Copy link
Member

chizhg commented Dec 2, 2020

/lifecycle frozen

@knative-prow-robot knative-prow-robot added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Dec 2, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/enhancement lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
Projects
None yet
Development

No branches or pull requests

3 participants