[create-pull-request] automated change

.github/workflows/release-workflow.yml

@@ -158,10 +158,10 @@ jobs:
     strategy:
       fail-fast: false
       matrix:
-        image: ["sharedpy3keras1.2", "sharedpy3keras2", "mpra-dragonn", "extended_coda", "mmsplice",
-          "mmsplice-mtsplice", "deepmel", "framepool", "kipoisplice", "deeptarget",
-          "attentivechrome", "bpnet-oskn", "seqvec", "deepflybrain", "aparent-site_probabilities",
-          "aparent-veff", "deepstarr"]  
+        image: ["sharedpy3keras1.2", "sharedpy3keras2", "mpra-dragonn", "extended_coda",
+          "mmsplice", "mmsplice-mtsplice", "deepmel", "framepool", "kipoisplice",
+          "deeptarget", "attentivechrome", "bpnet-oskn", "seqvec", "deepflybrain",
+          "aparent-site_probabilities", "aparent-veff", "deepstarr"]
     runs-on: ubuntu-latest
     env:
       SINGULARITY_PULL_FOLDER: "/home/runner/singularity/"

apptainer-1.0.1/.ci/e2e_triggers

@@ -0,0 +1,5 @@
+^internal/.*\.go$
+^cmd/.*\.go$
+^pkg/.*\.go$
+^e2e/
+^go\.mod$

apptainer-1.0.1/.github/ISSUE_TEMPLATE.md

@@ -0,0 +1,44 @@
+### Version of Apptainer:
+
+What version of Apptainer are you using? Run:
+
+```
+$ apptainer --version
+
+```
+
+
+<!-- please include command-line output in a code block -->
+
+### Expected behavior
+
+What did you expect to see when you do...?
+
+
+### Actual behavior
+
+What actually happend? Why was it incorrect?
+
+
+
+<!-- if this is a feature request, you can ignore this next part -->
+
+### Steps to reproduce this behavior
+
+How can others reproduce this issue/problem?
+
+
+### What OS/distro are you running
+
+```
+$ cat /etc/os-release
+
+
+```
+
+
+### How did you install Apptainer
+
+Write here how you installed Apptainer. Eg. RPM, source.
+
+

apptainer-1.0.1/.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,19 @@
+## Description of the Pull Request (PR):
+
+Write your description of the PR here. Be sure to include as much background,
+and details necessary for the reviewers to understand exactly what this is
+fixing or enhancing.
+
+
+### This fixes or addresses the following GitHub issues:
+
+ - Fixes #
+
+
+#### Before submitting a PR, make sure you have done the following:
+
+- Read the [Guidelines for Contributing](https://github.com/apptainer/apptainer/blob/main/CONTRIBUTING.md), and this PR conforms to the stated requirements.
+- Added changes to the [CHANGELOG](https://github.com/apptainer/apptainer/blob/main/CHANGELOG.md) if necessary according to the [Contribution Guidelines](https://github.com/apptainer/apptainer/blob/main/CONTRIBUTING.md)
+- Added tests to validate this PR, linted with `make check`  and tested this PR locally with a `make test`, and `make testall` if possible (see CONTRIBUTING.md).
+- Based this PR against the appropriate branch according to the [Contribution Guidelines](https://github.com/apptainer/apptainer/blob/main/CONTRIBUTING.md)
+- Added myself as a contributor to the [Contributors File](https://github.com/apptainer/apptainer/blob/main/CONTRIBUTORS.md)

apptainer-1.0.1/.github/dependabot.yml

@@ -0,0 +1,12 @@
+# To get started with Dependabot version updates, you'll need to specify which
+# package ecosystems to update and where the package manifests are located.
+# Please see the documentation for all configuration options:
+# https://help.github.com/github/administering-a-repository/configuration-options-for-dependency-updates
+
+version: 2
+updates:
+  - package-ecosystem: "gomod" # See documentation for possible values
+    directory: "/" # Location of package manifests
+    schedule:
+      interval: "daily"
+    target-branch: main

apptainer-1.0.1/.github/stale.yml

@@ -0,0 +1,61 @@
+# Configuration for probot-stale - https://github.com/probot/stale
+
+# Number of days of inactivity before an Issue or Pull Request becomes stale
+daysUntilStale: 180
+
+# Number of days of inactivity before an Issue or Pull Request with the stale label is closed.
+# Set to false to disable. If disabled, issues still need to be closed manually, but will remain marked as stale.
+daysUntilClose: 14
+
+# Only issues or pull requests with all of these labels are check if stale. Defaults to `[]` (disabled)
+onlyLabels: []
+
+# Issues or Pull Requests with these labels will never be considered stale. Set to `[]` to disable
+exemptLabels:
+  - pinned
+  - security
+  - "[Status] On Hold"
+
+# Set to true to ignore issues in a project (defaults to false)
+exemptProjects: false
+
+# Set to true to ignore issues in a milestone (defaults to false)
+exemptMilestones: false
+
+# Set to true to ignore issues with an assignee (defaults to false)
+exemptAssignees: false
+
+# Label to use when marking as stale
+staleLabel: stale
+
+# Comment to post when marking as stale. Set to `false` to disable
+markComment: >
+  This issue has been automatically marked as stale because it has not had
+  activity in over 180 days. It will be closed in 14 days if no further activity occurs. Thank you
+  for your contributions.
+
+# Comment to post when removing the stale label.
+# unmarkComment: >
+#   Your comment here.
+
+# Comment to post when closing a stale Issue or Pull Request.
+closeComment: >
+   This issue has been automatically closed because no response was provided within 14 days.
+
+# Limit the number of actions per hour, from 1-30. Default is 30
+limitPerRun: 30
+
+# Limit to only `issues` or `pulls`
+only: issues
+
+# Optionally, specify configuration settings that are specific to just 'issues' or 'pulls':
+# pulls:
+#   daysUntilStale: 30
+#   markComment: >
+#     This pull request has been automatically marked as stale because it has not had
+#     recent activity. It will be closed if no further activity occurs. Thank you
+#     for your contributions.
+
+# issues:
+#   exemptLabels:
+#     - confirmed