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

Utilize "not_found" state for GitLab CI Merge Status page #159

Closed
kalibyrn opened this issue Dec 15, 2015 · 0 comments
Closed

Utilize "not_found" state for GitLab CI Merge Status page #159

kalibyrn opened this issue Dec 15, 2015 · 0 comments
Labels
fix-pending
Milestone
1.2.0

Comments

@kalibyrn
Copy link

I think https://github.com/gitlabhq/gitlabhq/issues/7047 can probably be closed now if the plugin uses "not_found" instead of "unknown".
coder-hugo added a commit to coder-hugo/gitlab-plugin that referenced this issue Feb 26, 2016
@coder-hugo
Use status not_found instead of pending if there is currently no buil…
3303a7b 
…d for a given commit sha1 (fixes jenkinsci#159)
coder-hugo added a commit to coder-hugo/gitlab-plugin that referenced this issue Feb 27, 2016
@coder-hugo
Use status not_found instead of pending if there is currently no buil…
6b99f63 
…d for a given commit sha1 (fixes jenkinsci#159)
coder-hugo added a commit to coder-hugo/gitlab-plugin that referenced this issue Mar 2, 2016
@coder-hugo
Use status not_found instead of pending if there is currently no buil…
f2e0f27 
…d for a given commit sha1 (fixes jenkinsci#159)
coder-hugo added a commit to coder-hugo/gitlab-plugin that referenced this issue Mar 10, 2016
@coder-hugo
Use status not_found instead of pending if there is currently no buil…
3d533fd 
…d for a given commit sha1 (fixes jenkinsci#159)
@coder-hugo coder-hugo added this to the 1.2.0 milestone Mar 20, 2016
exceed-alae pushed a commit to exceed-alae/gitlab-plugin that referenced this issue May 20, 2022
@DavidTanner
Merge pull request jenkinsci#159 from arcivanov/issue_158
ad97d1a 
Fixing NPE and non-sensical behavior of the GHPRB
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
fix-pending
Projects
None yet
Milestone
1.2.0
Development

No branches or pull requests
2 participants
@kalibyrn @coder-hugo