Skip to content

Pull Request test check is failing if the PR is opened from the comunity #23053

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
Open
vinokurig opened this issue Jul 23, 2024 · 1 comment · May be fixed by eclipse-che/che-server#802
Open

Pull Request test check is failing if the PR is opened from the comunity #23053

vinokurig opened this issue Jul 23, 2024 · 1 comment · May be fixed by eclipse-che/che-server#802
Assignees
@vinokurig
Labels
area/che-server kind/bug Outline of a bug - must adhere to the bug report template. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. severity/P1 Has a major impact to usage or development of the system.

Comments

@vinokurig
Copy link
Contributor

Describe the bug

If a pull request to che-server repository is opened by a person outside eclipse organization, the pull request check is failing, see: eclipse-che/che-server#704

Che version

7.89@latest

Steps to reproduce

N/A

Expected behavior

The pull request test check must pass

Runtime

OpenShift

Screenshots

No response

Installation method

chectl/latest

Environment

macOS

Eclipse Che Logs

No response

Additional context

No response
@vinokurig vinokurig added the kind/bug Outline of a bug - must adhere to the bug report template. label Jul 23, 2024
@che-bot che-bot added the status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. label Jul 23, 2024
@vinokurig vinokurig mentioned this issue Jul 23, 2024
Closed
@dkwon17 dkwon17 added area/che-server severity/P1 Has a major impact to usage or development of the system. and removed status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. labels Jul 23, 2024
@che-bot
Copy link
Contributor

che-bot commented Jan 19, 2025

Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.

Mark the issue as fresh with /remove-lifecycle stale in a new comment.

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

Moderators: Add lifecycle/frozen label to avoid stale mode.

@che-bot che-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 19, 2025
@vinokurig vinokurig mentioned this issue Mar 13, 2025
Closed
9 tasks
@ibuziuk ibuziuk moved this to 📅 Planned in Eclipse Che Team A Backlog Mar 19, 2025
@ibuziuk ibuziuk mentioned this issue Mar 24, 2025
Closed
9 tasks
@vinokurig vinokurig linked a pull request May 1, 2025 that will close this issue
Open
9 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@vinokurig vinokurig

Labels
area/che-server kind/bug Outline of a bug - must adhere to the bug report template. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. severity/P1 Has a major impact to usage or development of the system.
Projects
Eclipse Che Team A Backlog
Status: 📅 Planned
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Skip docker related pull request check steps from a fork pr vinokurig/che-server
3 participants
@vinokurig @che-bot @dkwon17