From 1a9350f60bfa0ac95ba1a20317de449a10724201 Mon Sep 17 00:00:00 2001 From: Doug Burks Date: Tue, 23 Jan 2024 09:51:45 -0500 Subject: [PATCH 1/2] Update 2-4.yml --- .github/DISCUSSION_TEMPLATE/2-4.yml | 31 ++++------------------------- 1 file changed, 4 insertions(+), 27 deletions(-) diff --git a/.github/DISCUSSION_TEMPLATE/2-4.yml b/.github/DISCUSSION_TEMPLATE/2-4.yml index 8fb311a83a..94bf06afd7 100644 --- a/.github/DISCUSSION_TEMPLATE/2-4.yml +++ b/.github/DISCUSSION_TEMPLATE/2-4.yml @@ -9,12 +9,7 @@ body: description: Which version of Security Onion 2.4.x are you asking about? options: - - - 2.4.0 - - 2.4.1 - - 2.4.2 - - 2.4.3 - - 2.4.4 - - 2.4.5 + - 2.4 Pre-release (Beta, Release Candidate) - 2.4.10 - 2.4.20 - 2.4.30 @@ -178,27 +173,9 @@ body: - type: textarea attributes: label: Detail - description: Please read the placeholder and then provide detailed information to help us help you. + description: Please read our discussion guidelines at https://github.com/Security-Onion-Solutions/securityonion/discussions/1720 and then provide detailed information to help us help you. placeholder: >- - STOP! Please read these guidelines in their entirety before typing! - - Community Support is considered best effort and there are no guarantees and no SLAs. If you need private, priority, or enterprise support, please consider purchasing support from Security Onion Solutions. - - Please review the Github Community Guidelines (see link on the right side of the page). - - Please be patient, courteous, and respectful. Disrespectful messages can result in being banned. - - Before posting for help, check the Help, FAQ, and other sections of the documentation (https://docs.securityonion.net/) to see if your question has already been answered there. - - Please do not tag an individual in a discussion unless that individual has already volunteered to help you in that discussion. - - When creating your discussion, please put a relevant and descriptive title in the Title field and avoid generic titles like Help. When copying text from your Security Onion deployment to the discussion, please copy as plain text when possible rather than taking a screenshot of the text. This allows others to search for and find your text. - - Avoid typing in ALL CAPS as this looks like YELLING! - - If you need to include a large section of output, please do so as an attached file or Github gist rather than including the output directly in the reply itself. - - If you attach files, please make sure they are plain text format. No Word docs or PDFs please. + STOP! Before typing, please read our discussion guidelines at https://github.com/Security-Onion-Solutions/securityonion/discussions/1720 in their entirety! validations: required: true @@ -206,5 +183,5 @@ body: attributes: label: Guidelines options: - - label: I have read the above statement and can confirm my post is relevant to Security Onion 2.4. + - label: I have read the discussion guidelines at https://github.com/Security-Onion-Solutions/securityonion/discussions/1720 and assert that I have followed the guidelines. required: true From 9e98b409a5c0b8b8883be1b56be98dc8b339bddb Mon Sep 17 00:00:00 2001 From: Jason Ertel Date: Tue, 20 Feb 2024 16:00:41 -0500 Subject: [PATCH 2/2] thread locking --- .github/workflows/lock-threads.yml | 42 ++++++++++++++++++++++++++++++ 1 file changed, 42 insertions(+) create mode 100644 .github/workflows/lock-threads.yml diff --git a/.github/workflows/lock-threads.yml b/.github/workflows/lock-threads.yml new file mode 100644 index 0000000000..25e5d8c170 --- /dev/null +++ b/.github/workflows/lock-threads.yml @@ -0,0 +1,42 @@ +name: 'Lock Threads' + +on: + schedule: + - cron: '50 1 * * *' + workflow_dispatch: + +permissions: + issues: write + pull-requests: write + discussions: write + +concurrency: + group: lock-threads + +jobs: + close-threads: + runs-on: ubuntu-latest + permissions: + issues: write + pull-requests: write + steps: + - uses: actions/stale@v5 + with: + days-before-issue-stale: -1 + days-before-issue-close: 60 + stale-issue-message: "This issue is stale because it has been inactive for an extended period. Stale issues convey that the issue, while important to someone, is not critical enough for the author, or other community members to work on, sponsor, or otherwise shepherd the issue through to a resolution." + close-issue-message: "This issue was closed because it has been stale for an extended period. It will be automatically locked in 30 days, after which no further commenting will be available." + days-before-pr-stale: 45 + days-before-pr-close: 60 + stale-pr-message: "This PR is stale because it has been inactive for an extended period. The longer a PR remains stale the more out of date with the main branch it becomes." + close-pr-message: "This PR was closed because it has been stale for an extended period. It will be automatically locked in 30 days. If there is still a commitment to finishing this PR re-open it before it is locked." + + lock-threads: + runs-on: ubuntu-latest + steps: + - uses: jertel/lock-threads@main + with: + include-discussion-currently-open: true + discussion-inactive-days: 90 + issue-inactive-days: 30 + pr-inactive-days: 30