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

Fetching and using the bearer token #2

Merged
merged 1 commit into from
Sep 28, 2022
Merged

Fetching and using the bearer token #2

merged 1 commit into from
Sep 28, 2022

Conversation

emilkovacev
Copy link
Member

Every time I want to start up this project, I spend 30 or so minutes figuring out authorization. Instead, I figured it would be easier to put an example in the documentation to cut setup time and enable more commits in the future!

Proposed changes


Describe the big picture of your changes here to communicate to the maintainers why we should accept this pull request. If it fixes a bug or resolves a feature request, be sure to link to that issue.

Types of changes


What types of changes does your code introduce?
Put an x in the boxes that apply

  • Bugfix (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 (if none of the other choices apply)

Checklist


Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. This is simply a reminder of what we are going to look for before merging your code.

  • My changeset covers only what is described above (no extraneous changes)
  • Lint and unit tests pass locally with my changes
  • I have added tests that prove my fix is effective or that my feature works
  • I have added necessary documentation (if appropriate)
  • Any dependent changes have been merged downstream

Further comments


If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc...

Every time I want to start up this project, I spend 30 or so minutes figuring out authorization. Instead, I figured it would be easier to put an example in the documentation to cut setup time and enable more commits in the future!
@emilkovacev emilkovacev added the documentation Improvements or additions to documentation label Sep 21, 2022
@emilkovacev emilkovacev self-assigned this Sep 21, 2022
@jessehartloff jessehartloff merged commit 086614b into makeopensource:master Sep 28, 2022
@emilkovacev emilkovacev deleted the setup-auth-docs branch November 17, 2022 04:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Development

Successfully merging this pull request may close these issues.

2 participants