-
Notifications
You must be signed in to change notification settings - Fork 158
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
workflows: Add PR deployment action #313
Conversation
a2a2b80
to
d162b48
Compare
Any way to test it? |
Yes, the PR itself. The action fails unfortunately. |
I've made the changes you requested @gabrielmocanu. Let me know if you find a way to fix it. |
9fac7aa
to
c40f8a9
Compare
b334f52
to
014ea92
Compare
Yes, it is relevant. We don't have such a workflow in the |
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.
@teodutu , this looks good to me. Let's wait for @gabrielmocanu 's opinion and merge this as fast as possible.
d581073
to
d29e783
Compare
The action builds the rendered website and pushes it to the branch `gh-pages` in a directory named after the PR number. It then publishes a message containing the link where the website may be inspected. In order to trigger the workflow, label `needs-rendering` on the PR it's required. Signed-off-by: Teodor Dutu <[email protected]> Signed-off-by: Gabriel Mocanu <[email protected]>
d29e783
to
e2a0d6a
Compare
Tested it here: https://github.com/test-org-oeh/operating-systems/pull/3 |
The action builds the rendered website and pushes it to the
gh-pages
in a directory named after the PR number:refs/pull/<number>/merge
. It then publishes a message containing the link where the website may be inspected.I tested the action here: teodutu#8 (comment)