60643fe695
Update github actions to latest versions
...
Primarily to avoid the versions that are now deprecated, but also update
actions/upload-artifact to keep us up to date.
2024-02-05 16:34:47 +01:00
156b9a99e2
Set snap credentials via environment
...
The old method of using "with" is no longer supported.
2022-12-14 12:50:51 +01:00
64d3d60120
Use "npm update" to install dependencies
...
We don't want to build our npm package, just get our development
dependencies.
2022-11-07 17:24:26 +01:00
e674ee4d8e
Add translation workflow file
...
Just to make sure we continuously test that the tools work. This won't
actually update any translations.
2022-11-07 17:23:54 +01:00
a0c4214823
Use latest GitHub actions
...
The older ones are getting deprecated, so make the switch.
2022-10-13 16:20:28 +02:00
d5b8425d42
Use automatic version when building snap directly
...
Make it easier to build a snap from your working copy by removing the
restriction of having to modify the version field first.
2022-09-14 10:34:01 +02:00
99cf540e1a
Set a git version number on most builds
...
If it isn't a release then it is some form of development build and
should have a version that reflects that.
2021-11-09 16:32:49 +01:00
c2980d15e9
Only publish if we are in the original repo
...
This avoids people having failing actions in forks of our repo since
they don't have permission to publish things.
2021-11-09 16:32:34 +01:00
bbbcab692a
Make workflow if expressions multi line
...
To make them easier to read
2021-11-09 16:20:41 +01:00
8c09b99b4e
Fix typo in deploy workflow
2021-11-09 16:05:17 +01:00
303e5ef87b
Publish development builds to npm and snap
...
Gives us early warnings about problems, and allows people to test any
committed version.
2021-11-08 16:36:40 +01:00
a5499bbffe
Bump up node version for lint github action
...
Apparently the new eslint version doesn't work with the older version of
node that we were using. Asking for '@v2' seems to help. It's unclear
what version of node we get now though since v2 isn't as verbose in its
output.
2021-10-22 13:42:41 +02:00
0fd0d57fcd
Fix snapcraft publish step
...
A typo caused it to use the incorrect path
2021-09-09 11:27:51 +02:00
5a0cceb815
Change phrasing for discussion group link
...
It's listed with the issue templates, so make sure it follows the same
style in phrasing.
2021-01-15 16:16:38 +01:00
d56e042fee
Add link to discussion group from issues
...
So that people can easily find it and not file bug reports for
things that are just questions.
2021-01-15 16:14:40 +01:00
babd665c03
Hide link to create blank issues
...
We want users to use the templates so we don't miss any relevant
information.
2021-01-15 16:08:13 +01:00
4a8efa6bc9
Use snap actions instead of the broken container
...
The container didn't work properly for our base snap anyway.
2020-12-30 15:46:03 +01:00
cd9f535eb3
Package files directly in snapcraft.yaml
...
We don't need to convert things anymore, so reference files directly in
the snap yaml file.
2020-12-30 15:46:03 +01:00
23249c7263
Store result from NPM and snap builds
...
To ease debugging.
2020-12-30 15:46:03 +01:00
76aa3d1256
Run NPM and snap builds on every push
...
To make sure these things still build. That means we need to make the
actual deploy parts optional.
2020-12-30 13:40:03 +01:00
c01eb5e74d
Drop support for Internet Explorer
2020-10-15 18:53:51 +02:00
2654bcd354
Explicitly set NPM registry URL
...
Otherwise the action doesn't configure npm properly to authenticate and
our publish actions will fail with 404 errors.
2020-07-07 12:49:50 +02:00
ef5db94a89
Publish pre-releases to beta channels
...
Extra important for NPM which doesn't allow replacing a release once it
is published.
2020-07-03 16:00:04 +02:00
244c02c5ea
Deploy new snap on release
2020-06-26 14:48:32 +02:00
2835616b75
Use GitHub actions instead of Travis/Sauce Labs
...
The ability to use Sauce Labs for pull requests has now stopped working,
as Travis warned about several years ago. Instead run our tests directly
on GitHub on their various virtual machines.
2020-06-23 13:56:33 +02:00
5dad77b9d5
Add issue templates
...
We often have to ask for the same information for every new issue. Try to avoid this by using github's templates for issues.
2018-05-21 09:37:37 +02:00
Pierre Ossman
Samuel Mannehed