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

Psg 4895 use repo templates #85

Merged
merged 12 commits into from
Oct 23, 2024
Merged

Conversation

jenn-macfarlane
Copy link
Contributor

@jenn-macfarlane jenn-macfarlane commented Oct 21, 2024

Pull Request Template

What's New?

Uses repo templates to format README, LICENSE, and remove community files in favour of using organization community files.

Screenshots (if appropriate):

(The Passage logos will pick up theme change, this is just a screen shot from vscode):

Main README:
CleanShot 2024-10-22 at 14 39 39

Complete:
CleanShot 2024-10-22 at 09 47 24@2x

Flex:
CleanShot 2024-10-22 at 09 46 21@2x

Authentikit:
CleanShot 2024-10-22 at 09 47 39@2x

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

Checklist:

  • My code follows the style guidelines of this project
  • I have performed a self-review of my own code
  • I have manually tested my code thoroughly
  • I have added/updated inline documentation for public facing interfaces if relevant
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing integration and unit tests pass locally with my changes
  • Any dependent changes have been merged and published in downstream modules

Jira Ticket

Please add the Jira ticket number and link.

Additional context

Add any other context or screenshots about the pull request here.

@jenn-macfarlane
Copy link
Contributor Author

As of right now this PR is just updating the top-level README as the passage/passageflex readmes are auto-generated.

Couple questions:

  • do we want to keep the auto-generated READMEs given they contain info the docs don't currently have (eg. "Documentation for API Endpoints" sections)?
  • should I link to these auto-generated READMEs anywhere in the top-level one? My hunch is no as they're so specific

I'll also link to the appropriate anchor tag in the product tables in flutter/react-native where we reference Authentikit for ios/android and flex APIs.

README.md Outdated
<p>
You'll need a free Passage account and a Passkey Complete app set up in <a href="https://console.passage.id/">Passage Console</a> to get started. <br />
<sub><a href="https://docs.passage.id/home#passage-console">Learn more about Passage Console →</a></sub>
</p>

### Passkey Complete
Copy link
Contributor

Choose a reason for hiding this comment

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

Like the way you broke these up! It looks like Passkey Complete is duplicated, though, and it appears twice in the README (in addition to a section for Flex and Authentikit)

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Good catch, thanks!

Copy link
Contributor

@agebhardt agebhardt left a comment

Choose a reason for hiding this comment

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

Looks like there's a duplicate of Passkey Complete sections (most visible when browsing the README in the branch:
Here: https://github.com/passageidentity/passage-android/tree/PSG-4895-use-repo-templates?tab=readme-ov-file#passkey-complete
And here: https://github.com/passageidentity/passage-android/tree/PSG-4895-use-repo-templates?tab=readme-ov-file#passkey-complete-1

They are also slightly different 😅 though I think the second initialize block better aligns with our pattern :)

…tikit, passage, and passageflex and link appropriately
@jenn-macfarlane
Copy link
Contributor Author

Hi @agebhardt! Thanks for the catch. I've cleaned that up, given the main README a bit of a change - namely including a "prerequisites" section under each product because they differ (either setting up Flex/Complete/either in Console). I've also added new READMEs with the same content to each individual package, and updated the product tables within each to point to the repo folder where they are found.

Please take a look and let me know if I missed anything/if it makes sense this way - I've got mobile's blessing to add these.

README.md Outdated

### In passage-android

Use passage-android to implement [passage-android/passage](https://github.com/passageidentity/passage-android/passage) in your Android application to authenticate requests and manage users, [passage-android/passageflex](https://github.com/passageidentity/passage-android/passageflex) in your existing auth to use passkeys for registration, authentication, or added security on sensitive user actions, and [passage-android/authentikit](https://github.com/passageidentity/passage-android/authentikit) to gather data on your users' passkey readiness.
Copy link
Contributor Author

@jenn-macfarlane jenn-macfarlane Oct 22, 2024

Choose a reason for hiding this comment

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

This is a mouthful but what I came up with that didn't sound super redundant given the above. Took the flex desc from passage-js-flex README. Open to suggestions!


### In passage-android/authentikit

Use passage-android/authentikit to implement Passkey Ready in your Android application to gather data on your users' passkey readiness.
Copy link
Contributor Author

Choose a reason for hiding this comment

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

Feel free to suggest an edit (should match what's in main readme).

Copy link

@jenn-macfarlane jenn-macfarlane merged commit a1fd36f into main Oct 23, 2024
4 checks passed
@jenn-macfarlane jenn-macfarlane deleted the PSG-4895-use-repo-templates branch October 23, 2024 15:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants