Skip to content

feat(github-growth): allow hiding repos #52766

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

Merged
merged 2 commits into from
Jul 13, 2023

Conversation

cathteng
Copy link
Member

Allow setting a Repository object's status to ObjectStatus.HIDDEN.

For ER-1718

@github-actions github-actions bot added the Scope: Backend Automatically applied to PRs that change backend components label Jul 12, 2023
@codecov
Copy link

codecov bot commented Jul 12, 2023

Codecov Report

Merging #52766 (b207ea2) into master (9a020f6) will increase coverage by 0.00%.
The diff coverage is 100.00%.

Additional details and impacted files
@@           Coverage Diff           @@
##           master   #52766   +/-   ##
=======================================
  Coverage   79.37%   79.37%           
=======================================
  Files        4921     4921           
  Lines      206601   206603    +2     
  Branches    35315    35316    +1     
=======================================
+ Hits       163983   163997   +14     
+ Misses      37592    37584    -8     
+ Partials     5026     5022    -4     
Impacted Files Coverage Δ
...y/api/endpoints/organization_repository_details.py 84.41% <100.00%> (+0.41%) ⬆️

... and 5 files with indirect coverage changes

@cathteng cathteng requested review from a team and AniketDas-Tekky July 13, 2023 17:33
@cathteng cathteng marked this pull request as ready for review July 13, 2023 17:33
@@ -20,6 +20,7 @@ class RepositorySerializer(serializers.Serializer):
# XXX(dcramer): these are aliased, and we prefer 'active' over 'visible'
("visible", "visible"),
("active", "active"),
("hidden", "hidden"),
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just curious, why do we set choices as a tuple with duplicate values?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i think sometimes you can have different values of what you allow to be sent to the API and what the serializer outputs as the value https://github.com/getsentry/sentry/blob/master/src/sentry/api/validators/servicehook.py#L10

@cathteng cathteng merged commit e47172f into master Jul 13, 2023
@cathteng cathteng deleted the cathy/github-growth/allow-hiding-repo branch July 13, 2023 20:52
@github-actions github-actions bot locked and limited conversation to collaborators Jul 29, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Scope: Backend Automatically applied to PRs that change backend components
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants