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

Increase visibility of the EXPO_TOKEN link #168

Merged
merged 1 commit into from
Mar 17, 2022

Conversation

EvanBacon
Copy link
Contributor

Additional context

  • A bit overkill but there's no real harm in making every reference to the "token" a link to the token generator. I also added a spot where "EXPO_TOKEN" can be ⌘F'd

@EvanBacon EvanBacon requested a review from byCedric March 17, 2022 15:53
@byCedric byCedric merged commit 9fce70f into main Mar 17, 2022
@byCedric byCedric deleted the @evanbacon/docs/expo-token-notice branch March 17, 2022 16:44
@EvanBacon EvanBacon restored the @evanbacon/docs/expo-token-notice branch March 17, 2022 17:45
@byCedric byCedric deleted the @evanbacon/docs/expo-token-notice branch March 17, 2022 18:03
github-actions bot pushed a commit that referenced this pull request Mar 17, 2022
### [7.1.1](7.1.0...7.1.1) (2022-03-17)

### Bug fixes

* package tool escape path on windows ([#169](#169)) ([db9b5ce](db9b5ce)), closes [#167](#167)

### Other chores

* add tags syncing to the release workflow ([eb1ffb8](eb1ffb8))
* fix dirty repo preventing tag bump ([7cde8f8](7cde8f8))

### Documentation changes

* add direct link to expo access tokens ([1f38d16](1f38d16))
* increase visibility of the EXPO_TOKEN link ([#168](#168)) ([9fce70f](9fce70f))
* **preview-comment:** update expo-cli version to latest ([4681fcf](4681fcf))
* reword the assumptions on package manager ([459b567](459b567))
@github-actions
Copy link

🎉 This PR is included in version 7.1.1 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants