Commit Graph

9 Commits

Author SHA1 Message Date
Brent Baude
8cef2f4d10 Enhance issue reporting template
This PR adds a suggestion on the reporting template in github for people to run mac utilities like sw_vers and system_profiler utilities.  These utilities produce output like:

$ sw_vers
ProductName:		macOS
ProductVersion:		15.3.2
BuildVersion:		24D81
$ system_profiler SPHardwareDataType
Hardware:

    Hardware Overview:

      Model Name: Mac mini
      Model Identifier: Mac16,11
      Model Number: MCX44LL/A
      Chip: Apple M4 Pro
      Total Number of Cores: 12 (8 performance and 4 efficiency)
      Memory: 24 GB
      System Firmware Version: 11881.81.4
      OS Loader Version: 11881.81.4
      ... redacted

Signed-off-by: Brent Baude <bbaude@redhat.com>
2025-03-31 09:41:01 -05:00
Brent Baude
a8caebb5a3 Add documentation describing issues and support
We need to begin to able to prune various issues that are:

* stale
* unreproduceable
* will not fix
* others

As such, some sort of statement and somewhat policy leaning
documentation would be helpful.

As suggested in the review comments, ISSUE-EOL-POLICY.md was combined
with this document.  No links in our repository exist for this.

Signed-off-by: Brent Baude <bbaude@redhat.com>
2025-02-18 07:44:21 -06:00
Erik Sjölund
8757fe88ad github: add issue type as link to podman github discussions
Some issues reported in the podman github project contains a
question instead of a bug report or feature request. Make it
easier for users to find a place to ask questions.

Signed-off-by: Erik Sjölund <erik.sjolund@gmail.com>
2023-07-27 17:17:45 +02:00
Adam Jones
5aa52659b7 Fix bug report issue template README link
The relative link seems flakey: depending where you're creating the issue this may not take you to the right place.

For example, from https://github.com/containers/podman/issues/new it takes you to https://github.com/containers/podman/README.md, which does not exist.

To fix this, I've replaced it with an absolute link to the README for people to find the version easily. Other places in the same issue template use absolute paths to places in the repo e.g. the wiki, so I think this is acceptable.

Signed-off-by: Adam Jones <domdomegg+git@gmail.com>
2023-07-17 16:51:43 +01:00
Paul Holzinger
0714321de9 github: add issue type as link to podman-desktop
I see a lot of podman-desktop bug reports on the podman repo. This is
not the correct place to file these reports but many users seem to be
unaware of that. This is an attempt to point them in the right
direction. It should show up as extra entry in the issue type
selection so hopefully users while read that and follow the link in the
desktop repository.

See this link for the github docs about the configuration:
https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository#configuring-the-template-chooser

Signed-off-by: Paul Holzinger <pholzing@redhat.com>
2023-06-12 11:39:22 +02:00
Valentin Rothberg
04707f62d6 issue template: mention su
Mention that using `su` does not establish a proper login session
required for running rootless Podman.  It is a common and reoccurring
issue.  Mentioning that in the issue template may guide users into
resolving the issue before opening an issue.

Signed-off-by: Valentin Rothberg <vrothberg@redhat.com>
2023-05-10 14:27:35 +02:00
Paul Holzinger
3de409ad6a github: remove prefix from bugs/features
We already label the issue anyway and this results in reports without
an actual title so remove it. This leaves more space for an actual
useful title.

ref: https://github.com/containers/podman/discussions/17431

Signed-off-by: Paul Holzinger <pholzing@redhat.com>
2023-02-08 18:20:12 +01:00
salevdns
a1436d8fb5 Update bug_report.yaml
Render "podman info output" in YAML for better readability.

Signed-off-by: salevdns <24809481+salevdns@users.noreply.github.com>
2023-02-02 16:45:04 +01:00
Mohan Boddu
2b6cf1d072 Update the issue templates
Adding "Bug Report" and "Feature Request" templates, this will
help with filing the tickets and also finding the information
once filed.

Signed-off-by: Mohan Boddu <mboddu@redhat.com>
2022-11-30 14:06:29 -05:00