Skip to content
This repository has been archived by the owner on Mar 12, 2024. It is now read-only.

Watermelon as a team tool #276

Closed
baristaGeek opened this issue Sep 4, 2023 · 2 comments
Closed

Watermelon as a team tool #276

baristaGeek opened this issue Sep 4, 2023 · 2 comments
Assignees
@EstebanDalelR

Comments

@baristaGeek
Copy link
Collaborator

Right now our GitHub app contextualizes pull requests individually (only for the person who authorized Watermelon). These tools are expected to osmote information as a team: One person authorizes, and then everyone sees value.

To change this, we need to modify the stored procedure that searches for the token per username that calls getCodeContext, so that it searches for a "token per org" instead of "token per user".
@baristaGeek baristaGeek self-assigned this Sep 4, 2023
This was referenced Sep 7, 2023
Merged
Closed
Merged
@EstebanDalelR
Copy link
Member

On it.

Merged
8 tasks
Merged
@baristaGeek
Copy link
Collaborator Author

🎉🎉 closed with #326

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@EstebanDalelR EstebanDalelR

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@baristaGeek @EstebanDalelR