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

Watermelon using app token (team tool) #326

Merged
merged 25 commits into from
Oct 26, 2023
Merged

Conversation

EstebanDalelR
Copy link
Member

Description

Uses the app token instead of the user token to get info

Type of change

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Documentation update
  • Chore: cleanup/renaming, etc
  • RFC

Notes

Acceptance

@vercel
Copy link

vercel bot commented Oct 12, 2023

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
watermelon ❌ Failed (Inspect) Oct 26, 2023 10:36pm

@watermelon-copilot-for-code-review
Copy link

watermelon-copilot-for-code-review bot commented Oct 12, 2023

WatermelonAI Summary

The 25 commits in the Pull Request are primarily focused on improving the business logic related to team match and user information retrieval. Changes include adding more logging, fixing text clarity, improving parameter handling, simplifying code, and removing unnecessary code. Additionally, the use of the app token instead of the user token is implemented for retrieving information. Overall, these changes aim to enhance the process of team matching and user data management within the application.

GitHub PRs

Click here to login to Jira
Click here to login to Confluence
Slack Threads deactivated by EstebanDalelR

Notion Pages

Linear Tickets deactivated by EstebanDalelR
Click here to login to Asana
watermelon is an open repo and Watermelon will serve it for free.
🍉🫶

@EstebanDalelR EstebanDalelR changed the title Test using the installation id Watermelon using app token Oct 12, 2023
@EstebanDalelR EstebanDalelR changed the title Watermelon using app token Watermelon using app token (team tool) Oct 12, 2023
@@ -71,7 +75,7 @@ export default async function getAllServices({
});
return { error: error.message };
}
const [github, jira, confluence, slack, notion, linear, asana] =
const [github, teamGitHub, jira, confluence, slack, notion, linear, asana] =
Copy link
Collaborator

Choose a reason for hiding this comment

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

Nice idiomatic var name

Copy link
Collaborator

@baristaGeek baristaGeek left a comment

Choose a reason for hiding this comment

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

Testing notes:

Screen Shot 2023-10-13 at 12 22 43 PM

@@ -311,7 +314,7 @@ export async function POST(request: Request) {
owner,
issue_number: number,
repo,
body: "[Please login to Watermelon to see the results](https://app.watermelontools.com/)",
body: "[Please login to GitHub in Watermelon to see the results](https://app.watermelontools.com/)",
Copy link
Member Author

Choose a reason for hiding this comment

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

Fix to the text, there is no way to find a user without them logging in.
@baristaGeek

Copy link
Collaborator

@baristaGeek baristaGeek left a comment

Choose a reason for hiding this comment

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

Approving understanding the technical restrictions that we have.

@baristaGeek
Copy link
Collaborator

We must handle this case. I used my estebanvargasgarcia1994@gmail.com account.

Screen Shot 2023-10-24 at 12 09 55 PM

This is working properly now

@baristaGeek
Copy link
Collaborator

Ran with baristaGeek (estebanvargas94@gmail.com) which is part of the team and the team's query count didn't increase

Screen.Recording.2023-10-24.at.12.51.45.PM.mov

If this improves cool, but it's not a priority

@baristaGeek
Copy link
Collaborator

I think we're very close! I didn't get "user not registered" as the last time and actually got a successful response.

Is the only thing left to do actually executing the commenting -> detecting console logs -> labeling the PR flow?

Screen Shot 2023-10-25 at 5 23 54 PM

Copy link
Collaborator

@baristaGeek baristaGeek left a comment

Choose a reason for hiding this comment

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

Approving because it's working better than the current version of #334 (I recognize there are merge conflicts). The hard part works 🎉 🎉

We just have to fix placeholder={Teammate@${teamName.toLowerCase()}.com} which is something minor

@EstebanDalelR
Copy link
Member Author

We just have to fix placeholder={Teammate@${teamName.toLowerCase()}.com} which is something minor

Weird, this line hasn't ever been touched.

@EstebanDalelR
Copy link
Member Author

Anyway I opened #342 with that.

@baristaGeek
Copy link
Collaborator

We just have to fix placeholder={Teammate@${teamName.toLowerCase()}.com} which is something minor

Weird, this line hasn't ever been touched.

You're right this is broken in prod. Let's fix it. For now let's merge this

@EstebanDalelR EstebanDalelR merged commit 72b539f into dev Oct 26, 2023
2 of 3 checks passed
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants