improve issue query using search. #389
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
REST-API also has `in` parameter that can be set to `title` default is `title,description`. in may be added in future see: gitlab4j-api/issues/1172 Signed-off-by: Stefan Bischof <stbischof@bipolis.org>
|
Error response from ClearlyDefined HTTP 429 |
|
Did you test this? I have a vague recollection that this doesn't actually work. Normally, I'd have included a comment to that effect, so I can't be certain.
I assume that this message was intended for somewhere else. |
|
HTTP 429 - Was the error in the ci job. I did nit test it. That why i asked how tests are done in this. Thought that there may be a hidden Test somewhere that tests on real gitlab . |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
REST-API also has
inparameter that can be set totitledefault istitle,description.in may be added in future see: gitlab4j-api/issues/1172