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

API: Edit team breaks member and repository count #3600

Closed
2 of 7 tasks
nblock opened this issue Mar 1, 2018 · 2 comments · Fixed by #3831
Closed
2 of 7 tasks

API: Edit team breaks member and repository count #3600

nblock opened this issue Mar 1, 2018 · 2 comments · Fixed by #3831
Labels
Milestone

Comments

@nblock
Copy link

nblock commented Mar 1, 2018

  • Gitea version 1.3.3
  • Git version: 2.11.0
  • Operating system: Debian Stretch
  • Database (use [x]):
    • PostgreSQL
    • MySQL
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • No
    • Not relevant
  • Log gist:

Description

The following PATCH request to update an existing team breaks the member and repository count. 0 is shown while the team still lists all of its members and all of its repositories.

curl -X PATCH -H 'Authorization: token MYTOKEN' --data 'description=Jenkins and friends&name=CI&permission=read' https://gitea.example.com/api/v1/teams/49

Screenshots

Before
gitea_patch_before

After
gitea_patch_after

@nblock
Copy link
Author

nblock commented Mar 2, 2018

The swagger documentation for https://try.gitea.io/api/swagger#/organization/orgEditTeam specifies the content type as application/json while only form data works.

@lunny lunny added the type/bug label Mar 3, 2018
@lunny lunny added this to the 1.x.x milestone Mar 3, 2018
@thehowl
Copy link
Contributor

thehowl commented Apr 22, 2018

Can you please create another issue for the one you posted in the comment?

@lafriks lafriks modified the milestones: 1.x.x, 1.5.0 Apr 22, 2018
@go-gitea go-gitea locked and limited conversation to collaborators Nov 24, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants