You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
# Number of days of inactivity before an issue becomes stale
2
-
daysUntilStale: 60
3
-
# Number of days of inactivity before a stale issue is closed
4
-
daysUntilClose: 7
5
-
# Issues with these labels will never be considered stale
6
-
exemptLabels:
7
-
- pinned
8
-
- security
9
-
# Label to use when marking an issue as stale
10
-
staleLabel: stale
11
-
# Comment to post when marking an issue as stale. Set to `false` to disable
12
-
markComment: >
13
-
This issue has been automatically marked as stale because it has not had
14
-
recent activity. It will be closed if no further activity occurs. Thank you
15
-
for your contributions.
16
-
# Comment to post when closing a stale issue. Set to `false` to disable
17
-
closeComment: false
1
+
name: "Close stale issues and PRs"
2
+
on:
3
+
schedule:
4
+
- cron: "30 1 * * *"
5
+
6
+
jobs:
7
+
stale:
8
+
runs-on: ubuntu-latest
9
+
steps:
10
+
- name: Close Stale Issues
11
+
- uses: actions/stale@v4.1.1
12
+
with:
13
+
stale-issue-message: "This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days."
14
+
stale-pr-message: "This pull request is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days."
> This makes sure an unconditional `callsFake()` invoked on the same stub that was previously setup to throw will overwrite the previous behavior. This aligns it with the other behaviors.
<ahref="https://gitter.im/sinonjs/sinon?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge"><imgsrc="https://badges.gitter.im/Join%20Chat.svg"alt="Join the chat at https://gitter.im/sinonjs/sinon"></a>
Copy file name to clipboardexpand all lines: docs/README.md
+4-8
Original file line number
Diff line number
Diff line change
@@ -4,21 +4,17 @@ published: false
4
4
5
5
# Docs
6
6
7
-
This folder structure contains the markdown files that becomes the Sinon.JS documentation site published to GitHub Pages. Eventually this will replace the current site at https://sinonjs.org.
7
+
This folder structure contains the markdown files that is the Sinon.JS documentation site published to GitHub Pages.
8
8
9
9
See [CONTRIBUTING.md](CONTRIBUTING.md) for details on contributing documentation to Sinon.JS. This file also lists how to run the site locally.
10
10
11
11
## Documentation release process
12
12
13
-
Whenever a new release is created using `npm version`, the tree from `release-source/release/` is copied into its own folder under `releases/` with an appropriate name.
14
-
13
+
Whenever a new release is created using `npm version`, the tree from `release-source/release/` is copied into a folder under `releases/` with an appropriate name.
15
14
Likewise, the `_releases/release.md` file is copied into a file matching the release name.
16
15
17
-
### Example
18
-
19
-
Let's say that we're making a new `v2.0.3` release.
16
+
Currently, we keep a single folder per major release.
20
17
21
-
-`release-source/release/` is copied into a new folder `_releases/v2.0.3/`
22
-
-`release-source/release.md` is copied into a new file `_releases/v2.0.3.md`
18
+
See `scripts/postversion.sh` for details on the exact process, as it changes over time.
23
19
24
20
The release is packaged, tagged and pushed to GitHub. GitHub Pages will build a new site in a few minutes, and replace the old one.
0 commit comments