Skip to content

Commit cfc5c24

Browse files
committed
Copy .github directory from rand
1 parent 6120811 commit cfc5c24

File tree

11 files changed

+411
-0
lines changed

11 files changed

+411
-0
lines changed

.github/FUNDING.yml

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
1+
github: dhardy
Lines changed: 20 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,20 @@
1+
---
2+
name: Bug report
3+
about: Something doesn't work as expected
4+
title: ''
5+
labels: X-bug
6+
assignees: ''
7+
8+
---
9+
10+
## Summary
11+
12+
A clear and concise description of what the bug is.
13+
14+
What behaviour is expected, and why?
15+
16+
## Code sample
17+
18+
```rust
19+
// Code demonstrating the problem
20+
```
Lines changed: 16 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,16 @@
1+
---
2+
name: Compile issue
3+
about: Report / ask about a compilation issue
4+
title: ''
5+
labels: ''
6+
assignees: ''
7+
8+
---
9+
10+
# Common issues
11+
12+
**Problem**: `rand_hc::Hc128Rng: rand_core::SeedableRng` (or other RNG)
13+
14+
**Quick solution**: `cargo update`
15+
16+
**Details**: This happens when multiple versions of the `rand_core` crate are in use. Check your `Cargo.lock` file for all versions of `rand_core`. Note that some versions (0.2.2 and 0.3.1) are compatibility shims and are not a problem by themselves.
Lines changed: 18 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,18 @@
1+
---
2+
name: Feature request
3+
about: Suggest an idea for this project
4+
title: ''
5+
labels: ''
6+
assignees: ''
7+
8+
---
9+
10+
## Background
11+
12+
**What is your motivation?**
13+
14+
**What type of application is this?** (E.g. cryptography, game, numerical simulation)
15+
16+
## Feature request
17+
18+
<details here>

.github/ISSUE_TEMPLATE/other.md

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,10 @@
1+
---
2+
name: Other
3+
about: empty template
4+
title: ''
5+
labels: ''
6+
assignees: ''
7+
8+
---
9+
10+
Lines changed: 28 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,28 @@
1+
---
2+
name: Suggest a change
3+
about: Describe this issue template's purpose here.
4+
title: 'CHANGE: <summary>'
5+
labels: ''
6+
assignees: ''
7+
8+
---
9+
10+
A change request is considered a (small) Request-For-Comment, and requires a concrete proposal and motivation.
11+
12+
## Summary
13+
14+
How does this affect the API / end-user? (Include API-breaking changes, value-breaking changes and API additions.)
15+
16+
## Details
17+
18+
What changes does this require internally?
19+
20+
## Motivation
21+
22+
What is the motivation for this change?
23+
24+
Since every change has a cost (even if just API churn or extra code size), every change must have sufficient motivation. This is arguably the most important part of the RFC.
25+
26+
## Alternatives
27+
28+
Which alternatives might be considered, and why or why not?

.github/PULL_REQUEST_TEMPLATE.md

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,7 @@
1+
- [ ] Added a `CHANGELOG.md` entry
2+
3+
# Summary
4+
5+
# Motivation
6+
7+
# Details

.github/dependabot.yml

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,11 @@
1+
version: 2
2+
updates:
3+
- package-ecosystem: "cargo"
4+
directory: "/"
5+
schedule:
6+
interval: "monthly"
7+
open-pull-requests-limit: 10
8+
- package-ecosystem: "github-actions"
9+
directory: "/"
10+
schedule:
11+
interval: "monthly"

.github/workflows/benches.yml

Lines changed: 42 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,42 @@
1+
name: Benches
2+
3+
on:
4+
push:
5+
branches: [ master ]
6+
paths-ignore:
7+
- "**.md"
8+
- "examples/**"
9+
pull_request:
10+
branches: [ master ]
11+
paths-ignore:
12+
- "**.md"
13+
- "examples/**"
14+
15+
defaults:
16+
run:
17+
working-directory: ./benches
18+
19+
jobs:
20+
clippy-fmt:
21+
name: "Benches: Check Clippy and rustfmt"
22+
runs-on: ubuntu-latest
23+
steps:
24+
- uses: actions/checkout@v4
25+
- uses: dtolnay/rust-toolchain@master
26+
with:
27+
toolchain: stable
28+
components: clippy, rustfmt
29+
- name: Rustfmt
30+
run: cargo fmt -- --check
31+
- name: Clippy
32+
run: cargo clippy --all-targets -- -D warnings
33+
benches:
34+
name: "Benches: Test"
35+
runs-on: ubuntu-latest
36+
steps:
37+
- uses: actions/checkout@v4
38+
- uses: dtolnay/rust-toolchain@master
39+
with:
40+
toolchain: nightly
41+
- name: Test
42+
run: RUSTFLAGS=-Dwarnings cargo test --benches

.github/workflows/gh-pages.yml

Lines changed: 47 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,47 @@
1+
name: gh-pages
2+
3+
permissions:
4+
contents: read
5+
pages: write
6+
id-token: write
7+
8+
on:
9+
push:
10+
branches:
11+
- master
12+
13+
jobs:
14+
deploy:
15+
name: GH-pages documentation
16+
runs-on: ubuntu-latest
17+
environment:
18+
name: github-pages
19+
url: https://rust-random.github.io/rand/
20+
21+
steps:
22+
- name: Checkout
23+
uses: actions/checkout@v4
24+
25+
- name: Install toolchain
26+
uses: dtolnay/rust-toolchain@nightly
27+
28+
- name: Build docs
29+
env:
30+
RUSTDOCFLAGS: --cfg doc_cfg
31+
# --all builds all crates, but with default features for other crates (okay in this case)
32+
run: |
33+
cargo doc --all --all-features --no-deps
34+
cp utils/redirect.html target/doc/index.html
35+
rm target/doc/.lock
36+
37+
- name: Setup Pages
38+
uses: actions/configure-pages@v5
39+
40+
- name: Upload artifact
41+
uses: actions/upload-pages-artifact@v3
42+
with:
43+
path: './target/doc'
44+
45+
- name: Deploy to GitHub Pages
46+
id: deployment
47+
uses: actions/deploy-pages@v4

0 commit comments

Comments
 (0)