-
-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
TravisCI: include pages of all languages in archive #2567
Conversation
scripts/build.sh
Outdated
@@ -25,7 +25,7 @@ function build_archive { | |||
rm -f $TLDR_ARCHIVE | |||
|
|||
cd $TLDRHOME/ | |||
zip -r $TLDR_ARCHIVE pages/ LICENSE.md | |||
zip -r $TLDR_ARCHIVE pages/ pages.*/ LICENSE.md |
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.
Why not just pages*/
?
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.
Does it even work with the .
there, considering that the English pages directory does not have a suffix?
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.
@waldyrious, I assume it would in the initial one as it has pages/ pages.*/
so that would catch both.
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.
Oh yeah hahah, I totally misinterpreted the diff!
- zip -r $TLDR_ARCHIVE pages/ LICENSE.md
+ zip -r $TLDR_ARCHIVE pages/ pages.*/ LICENSE.md
Why not just `pages*/` ?
That should work as well. I just didn't think of it.
|
@arunisaac just for reference, github's squash option does not automatically interpret the |
Waldir Pimenta <[email protected]> writes:
@arunisaac just for reference, github's squash option does not
automatically interpret the `fixup!` directive in the commit message.
Yes, I suspected as much. In the future, should I use the "fixup!"
prefix? Or, is there some other preferred way for github to
automatically recognize commit messages to be squashed?
|
It's up to you. Maintainers should ask in case they need git actions from the contributor, anyway. In this case, what needed to happen was pretty straightforward (and could be done in the merge process) so I just went ahead and did it.
Not that I know of. :/ |
Now that we are supporting pages in multiple natural languages (#2339), we need to include all those pages in the tldr archive.