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

[Feature] [API] Option to fillter Issues based on participation #11179

Closed
6543 opened this issue Apr 22, 2020 · 3 comments · Fixed by #16174
Closed

[Feature] [API] Option to fillter Issues based on participation #11179

6543 opened this issue Apr 22, 2020 · 3 comments · Fixed by #16174
Labels
issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented modifies/api This PR adds API routes or modifies them type/feature Completely new functionality. Can only be merged if feature freeze is not active.

Comments

@6543
Copy link
Member

6543 commented Apr 22, 2020

fillter issues to only those who a user has participated ...

extend GET /repos/{owner}/{repo}/issues
@techknowlogick techknowlogick added the type/feature Completely new functionality. Can only be merged if feature freeze is not active. label Apr 23, 2020
@stale
Copy link

stale bot commented Jun 23, 2020

This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions.

@stale stale bot added the issue/stale label Jun 23, 2020
@adelowo
Copy link
Member

adelowo commented Jun 23, 2020

Not stale :)

@stale stale bot removed the issue/stale label Jun 23, 2020
@6543 6543 changed the title [Feature] [API] Option to fillter Issues based on prarticipation [Feature] [API] Option to fillter Issues based on participation Jun 23, 2020
@stale
Copy link

stale bot commented Aug 22, 2020

This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions.

@stale stale bot added the issue/stale label Aug 22, 2020
@zeripath zeripath added the issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented label Aug 22, 2020
@stale stale bot removed the issue/stale label Aug 22, 2020
@zeripath zeripath added the modifies/api This PR adds API routes or modifies them label Aug 22, 2020
@6543 6543 mentioned this issue Jun 16, 2021
Merged
@go-gitea go-gitea locked and limited conversation to collaborators Oct 19, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented modifies/api This PR adds API routes or modifies them type/feature Completely new functionality. Can only be merged if feature freeze is not active.
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

[API] ListIssues add more filters 6543-forks/gitea
4 participants
@techknowlogick @zeripath @adelowo @6543