-
-
Notifications
You must be signed in to change notification settings - Fork 8.5k
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
Include CI publish instructions for Azure Pipelines in docs #1208
Labels
difficulty: starter
Issues that are starter difficulty level, e.g. minimal tweaking with a clear test plan.
documentation
The issue is related to the documentation of Docusaurus
good first issue
If you are just getting started with Docusaurus, this issue should be a good place to begin.
v1
This issue is for Docusaurus 1
Comments
endiliey
added
the
documentation
The issue is related to the documentation of Docusaurus
label
Mar 20, 2019
I'm interested in contributing, could you give me more info? |
Any updates? |
yangshun
added
difficulty: starter
Issues that are starter difficulty level, e.g. minimal tweaking with a clear test plan.
good first issue
If you are just getting started with Docusaurus, this issue should be a good place to begin.
labels
Jun 5, 2020
I would like to work on this issue. |
Thanks @ayan-b for your PR doc for v1 is done, but keep this issue open as it's not yet done for v2 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
difficulty: starter
Issues that are starter difficulty level, e.g. minimal tweaking with a clear test plan.
documentation
The issue is related to the documentation of Docusaurus
good first issue
If you are just getting started with Docusaurus, this issue should be a good place to begin.
v1
This issue is for Docusaurus 1
📚 Documentation
It would be nice if the instructions for publishing via CI included instructions for Azure Pipelines as well: https://docusaurus.io/docs/en/publishing#automating-deployments-using-continuous-integration
Have you read the Contributing Guidelines on issues?
Yes
The text was updated successfully, but these errors were encountered: