| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
| |
This patch adds a new line to the github PR
template so users can assess that they have
obfuscated any password or similar from the
code they are submitting.
Signed-off-by: Jose Castillo <jcastillo@redhat.com>
|
| |
|
|
|
|
|
|
|
|
|
| |
Adding workdlow to publish the released sos to the latest/candidate channel
when the a new release is created via the tag. This ensures less mannual
intervention for future releases.
Update the snap creation for anyone building manually, and need python3-venv
as a build dependancy.
Signed-off-by: Arif Ali <arif.ali@canonical.com>
|
| |
|
|
|
|
|
|
|
|
|
| |
LGTM is shutting down shortly, as it has been folded into GH CodeQL. As
such, we need to switch over to using CodeQL to maintain automatic code
analysis.
Do this by using the provided CodeQL workflow configuration, and add a
config file to limit the analysis to the appropriate `sos/` directory.
Signed-off-by: Jake Hunsaker <jhunsake@redhat.com>
|
| |
|
|
|
|
|
|
| |
When installing via --danegerous, the aliases are not done
automatically, so create he sos alias, so that we can run
via "sos report"
Signed-off-by: Arif Ali <arif.ali@canonical.com>
|
| |
|
|
|
|
|
|
| |
The environment for the build doesn't seem to be refreshing between
runs, and hence sos from the snab binary location is not working.
Having the full path ensures that this doesn't fail
Signed-off-by: Arif Ali <arif.ali@canonical.com>
|
| |
|
|
|
|
|
|
|
|
| |
Add concutrrency to the job, so that if there is one already
running, then that would be cancelled
Remove the deb package, and that takes precedance with the path
do the test doesn't quite work
Signed-off-by: Arif Ali <arif.ali@canonical.com>
|
| |
|
|
|
|
|
|
| |
* snapcraft-channel was the old method, updating to release
* fetch all history, so that the version of the snap will be
based on the latest tag plus the number of commits since
Signed-off-by: Arif Ali <arif.ali@canonical.com>
|
| |
|
|
|
|
|
| |
Adds `--classic` to the snap installation test as part of the new GH
Action to push a new snap on `main` updates.
Signed-off-by: Jake Hunsaker <jhunsake@redhat.com>
|
| |
|
|
|
|
|
| |
When a any MRs or commits are added to the main branch then
automatically create a snap, and push to latest/edge channel
Signed-off-by: Arif Ali <arif.ali@canonical.com>
|
| |
|
|
|
|
|
|
| |
While using Github merging we don't need to track Resolves to
close PRs anymore. If existing (and not the PR currently on)
it still makes sense to use Resolves though.
Signed-off-by: Bryan Quigley <code@bryanquigley.com>
|
| |
|
|
|
|
| |
Resolves: #1815
Signed-off-by: Pablo Iranzo Gómez <Pablo.Iranzo@gmail.com>
|
| |
|
|
|
|
|
| |
Resolves: #1814
Signed-off-by: Pablo Iranzo Gómez <Pablo.Iranzo@gmail.com>
Signed-off-by: Bryn M. Reeves <bmr@redhat.com>
|
| |
|
|
| |
Signed-off-by: Adam Stokes <battlemidget@users.noreply.github.com>
|
|
|
This includes information for users wishing to submit PR's and is visible during
their creation of the PR. This allows them to validate that they are providing
all necessary requirements prior to submitting and should reduce the amount of
back and forth we do asking users to follow our guidelines.
Fixes #1021
Signed-off-by: Adam Stokes <battlemidget@users.noreply.github.com>
|
