This repository has been archived by the owner on May 18, 2021. It is now read-only.
Update branch without overwriting? #34
Comments
If I remember correctly that was done as a simple way to avoid conflicts.
@ljharb I won't have time to look into this in the next few weeks, but it sounds good to me, and I'm fine with this change! |
alrra
added a commit
that referenced
this issue
Feb 19, 2021
Deprecate project as: * Travis CI's new pricing plan¹ has effectively dropped support for open source, so people are migrating² away from Travis CI (I did the same quite some time ago). * This project hasn't been maintain in years, nor are there any plans to do so in the future. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ¹ https://blog.travis-ci.com/2020-11-02-travis-ci-new-billing ² ljharb/object.assign#81 tc39/ecma262#2260 Close: #30 Close: #31 Close: #32 Close: #33 Close: #34
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
We use this to update the gh-pages branch, but every time, it uses
git initand starts a fresh branch. Is there any way it could keep the history? That way, I could use a build command that builds - for example - each SHA separately, and keep all of them intact for historical perusal.The text was updated successfully, but these errors were encountered: