代码拉取完成,页面将自动刷新
同步操作将从 duoyuntian/piskel 强制同步,此操作会覆盖自 Fork 仓库以来所做的任何修改,且无法恢复!!!
确定后同步将在后台操作,完成时将刷新页面,请耐心等待。
retrieve source code and dependencies
git clone https://github.com/piskelapp/piskel
git clone https://github.com/piskelapp/piskel-website
prepare the release
piskel-website
clone, checkout the master
branch, not the release
. The release branch is similar to the master branch, except it doesn't ignore the statics files coming from the piskel
project. The idea is that we can easily checkout the release branch to do a new release, without having to rebuild piskel, in case nothing changed in piskel itself. We will switch to the release branch when we perform the final release.piskel
clone, create a new branch for the release git checkout -b vX.Y
grunt && node bin/copy-to-piskel-website.js
local test
vX.Y
branch) and push it.beta test
master
) and push it.check caches...
background-image: url(../img/icons@2x.png?20181125);
or <script type="text/javascript" src="/static/js/piskel-animated-preview.js?20181124"></script>
. Erk.finalize the release
piskel
update version in package.json. Remove the "-SNAPSHOT" at the end and commit the change, with a commit message such as release: bump version to vX.Y
.piskel-website
checkout the release
branch. Rebase it on master (that's pretty bad, we should probably cherry pick all the changes between the two branches...)piskel-website
run git status
to check that there are a bunch of changes to commit. (test locally again if you are paranoid)piskel-website
commit the current changes with a commit message such as update statics for release vX.Y
post release
vX+1.0-SNAPSHOT
此处可能存在不合适展示的内容,页面不予展示。您可通过相关编辑功能自查并修改。
如您确认内容无涉及 不当用语 / 纯广告导流 / 暴力 / 低俗色情 / 侵权 / 盗版 / 虚假 / 无价值内容或违法国家有关法律法规的内容,可点击提交进行申诉,我们将尽快为您处理。