aboutsummaryrefslogtreecommitdiffstats
path: root/.github
AgeCommit message (Collapse)Author
2019-10-26GitHub Actions: one more set of typos fixedGravatar Dirk Hohndel
I am at a loss for words. Especially as we didn't need those quotes in the first place. What was I thinking? Signed-off-by: Dirk Hohndel <dirk@hohndel.org>
2019-10-25GitHub Actions: fix several errors in previous commitsGravatar Dirk Hohndel
I have no excuse. Signed-off-by: Dirk Hohndel <dirk@hohndel.org>
2019-10-25GitHub Actions: add apt-get update before installing curlGravatar Dirk Hohndel
Signed-off-by: Dirk Hohndel <dirk@hohndel.org>
2019-10-25GitHub Actions: only build pushes into and PR against masterGravatar Dirk Hohndel
This should fix the odd double builds for people who create branches for pull requests in the main repository. Signed-off-by: Dirk Hohndel <dirk@hohndel.org>
2019-10-25GitHub Actions: push to transfer.sh for PRs, post release for pushesGravatar Dirk Hohndel
This means that PRs from people using the main repo for their staging branches will get both transfer.sh and a release. Signed-off-by: Dirk Hohndel <dirk@hohndel.org>
2019-10-25GitHub Actions: run them on pull requests as wellGravatar Dirk Hohndel
I wonder if this will cause issues where the actions sometimes run twice. But we'll deal with that rather than dealing with not having the tests on pull requests. Signed-off-by: Dirk Hohndel <dirk@hohndel.org>
2019-10-23GitHub Actions: Add automatic coverity scanGravatar Anton Lundin
This adds a automatic coverity scan build based on linux-bionic-5.9.yml Signed-off-by: Anton Lundin <glance@acc.umu.se>
2019-10-20GitHub Actions: fix logic error for new tagsGravatar Dirk Hohndel
It is clear why this wasn't caught in my testing, but the bug should have been really obvious simply reading through the code. Signed-off-by: Dirk Hohndel <dirk@hohndel.org>
2019-10-19GitHub Action: add iOS buildGravatar Dirk Hohndel
This is incredibly brute force, downloading a 3+GB installer and installing all of the Qt/iOS binaries. This first attempt is mainly to get an idea how long this will take and if this will fit within the size constraints of the build VM. This commit doesn't even try to build, yet. Signed-off-by: Dirk Hohndel <dirk@hohndel.org>
2019-10-18GitHub Actions: add Linux Bionic / Qt 5.9 buildGravatar Dirk Hohndel
No artifacts from this build are preserved, this is just to make sure that we can still build the desktop version against Qt 5.9. Signed-off-by: Dirk Hohndel <dirk@hohndel.org>
2019-10-18GitHub Actions: add Android buildGravatar Dirk Hohndel
Signed-off-by: Dirk Hohndel <dirk@hohndel.org>
2019-10-18GitHub Actions: improve naming and location of filesGravatar Dirk Hohndel
Just to make things a little more consistent. Signed-off-by: Dirk Hohndel <dirk@hohndel.org>
2019-10-18GitHub Actions: support creation of releases based on tagsGravatar Dirk Hohndel
And fix parsing of ref. Signed-off-by: Dirk Hohndel <dirk@hohndel.org>
2019-10-18GitHub Actions: post releasesGravatar Dirk Hohndel
This so far just works on push and hopefullt pull requests, not for tags and therefore actual releases. In order not to conflict with the binaries from Travis, I changed the name to "ci-release" instead of "continuous". Signed-off-by: Dirk Hohndel <dirk@hohndel.org>
2019-10-18GitHub Actions: build Windows binariesGravatar Dirk Hohndel
Signed-off-by: Dirk Hohndel <dirk@hohndel.org>
2019-10-16GitHub Actions: add Linux Qt 5.12 container buildGravatar Dirk Hohndel
The AppImage works - I just need to figure out how to post releases. For now it'a available on the Actions page as Artifact. Signed-off-by: Dirk Hohndel <dirk@hohndel.org>
2019-10-14GitHub Actions: first CI/CD build for Mac based on GitHub ActionsGravatar Dirk Hohndel
This feature is in beta right now and might change without notice, but instead of dealing with the broken Travis Mac builds, this does seem progress. The build artifact seems to work, but it's a bit more painful to get to. Go to https://github.com/Subsurface-divelog/subsurface/actions and click on the corresponding run - it's then in the top right corner under Artifacts. The one oddity is that after unzipping the file you need to manually make Contents/MacOS/Subsurface executable. Signed-off-by: Dirk Hohndel <dirk@hohndel.org>
2017-11-28release-notes: use CHANGELOG.mdGravatar Lubomir I. Ivanov
Add a file CHANGELOG.md in the root Subsurface directory and track this file with the `-text merge=union` attribute. This prevents merge conflicts if release notes are added on top of the file by different commits. Also, make ReleaseNotes/ReleaseNotes.txt point to that file. Signed-off-by: Lubomir I. Ivanov <neolit123@gmail.com>
2017-11-16github: update PR template with 'documentation-change'Gravatar Lubomir I. Ivanov
Add a 'Documentation change' section to the PR body. This instructs the PR submitter to edit the section with notes for the team editing the documentation. If a PR has such notes, a maintainer should then apply the needs-documentation-change label, so that the documentation team can easily filter such PRs by label. Suggested-by: Miika Turkia <miika.turkia@gmail.com> Signed-off-by: Lubomir I. Ivanov <neolit123@gmail.com>
2017-11-16github: improve the issue templateGravatar Lubomir I. Ivanov
1) Add new description types: - 'Code cleanup' - 'Build system change' 2) Add a 'Release note' section: The idea with this is that if you make a change which is worthy of a release note in ReleaseNotes.txt, it would be best to outline it here but also in the .txt. This basically means that the PR should also touch ReleaseNotes.txt with an extra patch. Signed-off-by: Lubomir I. Ivanov <neolit123@gmail.com>
2017-10-28Small changes to the issue templateGravatar Dirk Hohndel
This way hopefully more people will tell us right away which localization they are running in. Signed-off-by: Dirk Hohndel <dirk@hohndel.org>
2017-09-26github: add templates for pull requests and issue reportsGravatar Lubomir I. Ivanov
.github/ISSUE_TEMPLATE.md will be used when the Github users create new issues. .github/PULL_REQUEST_TEMPLATE.md will be used when the Github users create new pull requests. The markdown supports HTML comments (<!-- comment -->), which can instruct the Github user how to create a detailed PR or issue report. Most big Github projects use such templates and these can help the collaborators to examine the PRs and ISSUES faster. Fixes #598 Reviewed-by: Dirk Hohndel <dirk@hohndel.org> Reviewed-by: Jan Mulder <jlmulder@xs4all.nl> Signed-off-by: Lubomir I. Ivanov <neolit123@gmail.com> Signed-off-by: Miika Turkia <miika.turkia@gmail.com>