You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+6Lines changed: 6 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -53,6 +53,8 @@ Output format of any non-plumbing command can change in non-backward-compatible
53
53
1. Make sure that build for `master` passes on [Travis CI](https://travis-ci.org/VirtusLab/git-machete/branches).
54
54
55
55
1. Verify that a build started for [Snap](https://build.snapcraft.io/user/VirtusLab/git-machete).
56
+
If not, check build.snapcraft.io webhook on Github (under Settings > Webhooks) -
57
+
sometimes the build system responds with 500 status for no clear reason, in such case `Redeliver` the call.
56
58
Once ready, install the `latest/edge` revision locally (`sudo snap install --edge git-machete`)
57
59
and verify that it works correctly, esp. wrt. push/pull via ssh/https and editor (`git machete edit` and interactive rebases).
58
60
@@ -66,17 +68,20 @@ Output format of any non-plumbing command can change in non-backward-compatible
66
68
67
69
1. Verify that the release has been created on [Github](https://github.com/VirtusLab/git-machete/releases)
68
70
and that a `git-machete-VERSION-1.noarch.rpm` file is present under the Assets.
71
+
69
72
Fix the formatting in the description manually by copy-pasting the tag description
70
73
(see [this answer](https://github.community/t5/How-to-use-Git-and-GitHub/add-release-notes-to-git-remote-tag-from-command-line/m-p/22343/highlight/true#M6488)
71
74
for more details on why it's not automated as well).
72
75
73
76
1. Verify that the latest version is uploaded to [PyPI](https://pypi.org/project/git-machete).
74
77
75
78
1. Verify that the latest commit in [VirtusLab/homebrew-git-machete](https://github.com/VirtusLab/homebrew-git-machete) tap repo refers to the latest version.
79
+
76
80
Re-run the latest build for `orphan/brew-package-check` branch on [Travis CI](https://travis-ci.org/VirtusLab/git-machete/branches).
77
81
Inspect the job output and verify that the latest version gets correctly installed on Mac OS X (esp. see the output of `git machete --version`).
78
82
79
83
1. Verify that a build started on [git-machete PPA](https://launchpad.net/~virtuslab/+archive/ubuntu/git-machete/+packages).
84
+
80
85
Once the new version package is published and the old one is removed (typically takes around 20-30 min),
81
86
follow the instructions from [ci/apt-ppa-test-install/README.md](https://github.com/VirtusLab/git-machete/tree/master/ci/apt-ppa-test-install).
82
87
Inspect the output of `docker-compose` and verify that the latest version gets correctly installed on Ubuntu (esp. see the output of `git machete --version`).
@@ -88,5 +93,6 @@ Output format of any non-plumbing command can change in non-backward-compatible
88
93
If the release introduces significant changes/critical bugfixes, please [flag the package as out of date](https://aur.archlinux.org/pkgbase/git-machete/flag).
89
94
90
95
1. A [git-machete package](https://nixos.org/nixos/packages.html?channel=nixos-unstable&query=git-machete) is available for NixOS.
96
+
91
97
[Version-bump PRs to NixOS/nixpkgs](https://github.com/NixOS/nixpkgs/pulls?q=is%3Apr+git-machete) are opened by a semi-automatic update on an irregular basis.
92
98
There is an issue ([#79](https://github.com/VirtusLab/git-machete/issues/79)) for opening version-bump PRs automatically on each release.
0 commit comments