mirror of
https://github.com/rustfs/rustfs.git
synced 2026-10-05 12:42:20 +00:00
edcc81a8fd
* ci: replace ubuntu-latest runner with sm-standard-2 across workflows * ci: keep scheduled-validation monitors on hosted runners The freshness and watchdog jobs report stalled scheduled validations. Running them on the same sm-standard-2 pool means a pool outage stalls the monitors too, so nothing reports it. --------- Co-authored-by: overtrue <anzhengchao@gmail.com>
43 lines
1.8 KiB
YAML
43 lines
1.8 KiB
YAML
# Copyright 2024 RustFS Team
|
|
#
|
|
# Licensed under the Apache License, Version 2.0 (the "License");
|
|
# you may not use this file except in compliance with the License.
|
|
# You may obtain a copy of the License at
|
|
#
|
|
# http://www.apache.org/licenses/LICENSE-2.0
|
|
#
|
|
# Unless required by applicable law or agreed to in writing, software
|
|
# distributed under the License is distributed on an "AS IS" BASIS,
|
|
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
# See the License for the specific language governing permissions and
|
|
# limitations under the License.
|
|
|
|
# DISABLED. This workflow is switched off in the repository's Actions settings
|
|
# (state: disabled_manually) and does not run on any trigger, including its cron
|
|
# and workflow_dispatch. That state lives in GitHub's UI and is invisible when
|
|
# reading this file, which has already misled at least one audit — hence this
|
|
# banner. Re-enabling is a UI action; anyone doing so should first check that the
|
|
# workflow still matches the current CI layout. See rustfs/backlog#1603.
|
|
#
|
|
name: "Mark stale issues"
|
|
on:
|
|
schedule:
|
|
- cron: "30 1 * * *"
|
|
|
|
jobs:
|
|
stale:
|
|
runs-on: sm-standard-2
|
|
timeout-minutes: 30
|
|
steps:
|
|
- uses: actions/stale@4391f3da665fdf50b6810c1a66712fb9ba21aa93 # v11.0.0
|
|
with:
|
|
repo-token: ${{ secrets.GITHUB_TOKEN }}
|
|
stale-issue-message: 'This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.'
|
|
stale-issue-label: 'stale'
|
|
## Mark if there is no activity for more than 7 days
|
|
days-before-stale: 7
|
|
# If no one responds after 3 days, the tag will be closed.
|
|
days-before-close: 3
|
|
# These tags are exempt and will not close automatically.
|
|
exempt-issue-labels: 'pinned,security'
|