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

feat(gh-pages-publisher): force-push without history #7

Merged
merged 2 commits into from
Dec 13, 2018

Conversation

eladb
Copy link
Contributor

@eladb eladb commented Dec 13, 2018

to avoid bloating the gh-pages branch, the publisher
now will always force-push the contents of the site
with no git history.

Also, allow specifying a different branch name for
gh-pages.

Issue #, if available:

Description of changes:

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

to avoid bloating the gh-pages branch, the publisher
now will always force-push the contents of the site
with no git history.

Also, allow specifying a different branch name for
gh-pages.
@eladb eladb requested a review from RomainMuller December 13, 2018 11:55
lib/publishing/docs/publish-docs.sh Show resolved Hide resolved
README.md Show resolved Hide resolved
@eladb eladb merged commit e062ab7 into master Dec 13, 2018
@eladb eladb deleted the benisrae/docs-force-push branch December 13, 2018 12:44
@eladb eladb mentioned this pull request Dec 13, 2018
RomainMuller pushed a commit that referenced this pull request Dec 13, 2018
* **pipeline**: concurrency limit ([#9](#9))
* **gh-pages-publisher**: force-push without history ([#7](#7))
* **pipeline**: send email notifications on any action failure ([#10](#10))
* **github-releases**: if changelog doesn't exist, don't include release notes ([#8](#8))
* **pipeline**: raise an alarm when any stages are in a Failed state ([#6](#6))
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants