-
Notifications
You must be signed in to change notification settings - Fork 18
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
align environment variable name with docusaurus instructions #77
Conversation
@@ -15,4 +15,4 @@ jobs: | |||
- name: Publish ${{ github.ref }} | |||
run: sbt docs/docusaurusPublishGhpages | |||
env: | |||
GITHUB_DEPLOY_KEY: ${{ secrets.GITHUB_DEPLOY_KEY }} | |||
GIT_DEPLOY_KEY: ${{ secrets.GIT_DEPLOY_KEY }} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it's no matter how we define the env var in secrets, but I thought it should be GITHUB_DEPLOY_KEY
in CI as done in Scalafix, for example https://github.com/scalacenter/scalafix/blob/main/.github/workflows/deploy-website.yml#L17
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, I'm pretty confident it should be GITHUB_DEPLOY_KEY
in CI https://github.com/search?q=org%3Ascalacenter%20GITHUB_DEPLOY_KEY&type=code
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Perhaps the mdoc website is a little bit outdated 🤷🏻
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can't think why it would matter what it's called as long as we're consistent 🤷
yay, it's alive https://scalacenter.github.io/scalac-profiling/ |
yay |
No description provided.