Skip to content

Commit da6462e

Browse files
gutytoxgutytox
committed
initial commit
0 parents  commit da6462e

File tree

153 files changed

+8705
-0
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

153 files changed

+8705
-0
lines changed

‎.github/CODE_OF_CONDUCT.md

+73
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,73 @@
1+
# Contributor Covenant Code of Conduct
2+
3+
## Our Pledge
4+
5+
In the interest of fostering an open and welcoming environment, we as
6+
contributors and maintainers pledge to making participation in our project and
7+
our community a harassment-free experience for everyone, regardless of age, body
8+
size, disability, ethnicity, sex characteristics, gender identity and expression,
9+
level of experience, education, socio-economic status, nationality, personal
10+
appearance, race, religion, or sexual identity and orientation.
11+
12+
## Our Standards
13+
14+
Examples of behavior that contributes to creating a positive environment include:
15+
16+
* Using welcoming and inclusive language
17+
* Being respectful of differing viewpoints and experiences
18+
* Gracefully accepting constructive criticism
19+
* Focusing on what is best for the community
20+
* Showing empathy towards other community members
21+
22+
Examples of unacceptable behavior by participants include:
23+
24+
* The use of sexualized language or imagery and unwelcome sexual attention or advances
25+
* Trolling, insulting/derogatory comments, and personal or political attacks
26+
* Public or private harassment
27+
* Publishing others' private information, such as a physical or electronic address, without explicit permission
28+
* Other conduct which could reasonably be considered inappropriate in a
29+
professional setting
30+
31+
## Our Responsibilities
32+
33+
Project maintainers are responsible for clarifying the standards of acceptable
34+
behavior and are expected to take appropriate and fair corrective action in
35+
response to any instances of unacceptable behavior.
36+
37+
Project maintainers have the right and responsibility to remove, edit, or
38+
reject comments, commits, code, wiki edits, issues, and other contributions
39+
that are not aligned to this Code of Conduct, or to ban temporarily or
40+
permanently any contributor for other behaviors that they deem inappropriate,
41+
threatening, offensive, or harmful.
42+
43+
## Scope
44+
45+
This Code of Conduct applies both within project spaces and in public spaces
46+
when an individual is representing the project or its community. Examples of
47+
representing a project or community include using an official project e-mail
48+
address, posting via an official social media account, or acting as an appointed
49+
representative at an online or offline event. Representation of a project may be
50+
further defined and clarified by project maintainers.
51+
52+
## Enforcement
53+
54+
Instances of abusive, harassing, or otherwise unacceptable behavior may be
55+
reported by contacting the project team at `[email protected]`. All
56+
complaints will be reviewed and investigated and will result in a response that
57+
is deemed necessary and appropriate to the circumstances. The project team is
58+
obligated to maintain confidentiality with regard to the reporter of an incident.
59+
Further details of specific enforcement policies may be posted separately.
60+
61+
Project maintainers who do not follow or enforce the Code of Conduct in good
62+
faith may face temporary or permanent repercussions as determined by other
63+
members of the project's leadership.
64+
65+
## Attribution
66+
67+
This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
68+
available at <https://www.contributor-covenant.org/version/1/4/code-of-conduct.html>
69+
70+
For answers to common questions about this code of conduct, see
71+
<https://www.contributor-covenant.org/faq>
72+
73+
[homepage]: https://www.contributor-covenant.org

‎.github/CONTRIBUTING.md

+16
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,16 @@
1+
# How to Contribute
2+
3+
I want to thank you for sparing a time to improve this project! Here are some guidelines for contributing：
4+
5+
To ensure that the blog design is not confused, this project does not accept suggestions for design changes, such as color scheme, fonts, typography, etc. If your request is about an enhancement, it is recommended to first submit a [`Feature Request`](https://github.com/cotes2020/jekyll-theme-chirpy/issues/new?labels=enhancement&template=feature_request.md) issue to discuss whether your idea fits the project.
6+
7+
Generally, contribute to the project by:
8+
9+
1. Fork this project on GitHub and clone it locally.
10+
2. Create a new branch from `master` and give it a descriptive name (e.g., `my-new-feature`, `fix-a-bug`).
11+
3. After completing the development, commit and push to remote.
12+
4. Submit a new pull request.
13+
14+
---
15+
16+
:tada: Your volunteering will make the open source world more beautiful, thanks again! :tada:

‎.github/FUNDING.yml

+1
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
1+
custom: ['https://www.buymeacoffee.com/coteschung', 'https://cotes.gitee.io/alipay-wechat-donation']

‎.github/ISSUE_TEMPLATE/bug_report.md

+53
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,53 @@
1+
---
2+
name: Bug Report
3+
about: Create a report to help us improve
4+
labels: bug
5+
---
6+
7+
<!-- Note: Please follow the template to open a new issue, otherwise your question will probably be ignored. If you are new to Jekyll or Github Pages, you may be misreporting bugs. When you are not sure if this is a bug, choose to the `Question` type instead. -->
8+
9+
10+
## Checklist
11+
<!-- Please complete the following list of tasks, and then check it by change the "[ ]" to "[x]" -->
12+
- [ ] I have read the [tutorials](https://chirpy.cotes.info/categories/tutorial/) and know the correct effect of the functional design.
13+
- [ ] There are no similar reports on existing issues (including closed ones).
14+
- [ ] I found the bug on the latest code of `master` branch.
15+
16+
## Describe the bug
17+
<!-- A clear and concise description of what the bug is. -->
18+
19+
### To Reproduce
20+
21+
Steps to reproduce the behavior:
22+
23+
1. Go to '...'
24+
2. Click on '....'
25+
3. Scroll down to '....'
26+
4. See error
27+
28+
### Expected behavior
29+
<!-- A clear and concise description of what you expected to happen. -->
30+
31+
### Screenshots
32+
<!-- If applicable, add screenshots to help explain your problem. -->
33+
34+
### Software
35+
<!-- Please complete the following information -->
36+
- Ruby version: [by running: `ruby -v`]
37+
- Gem version: [by running: `gem -v`]
38+
- Bundler version: [by running: `bundle -v`]
39+
- Jekyll version: [by running: `bundle list | grep " jekyll "`]
40+
41+
### Desktop
42+
<!-- Please complete the following information -->
43+
- OS: [e.g. macOS 10.15.6]
44+
- Browser: [e.g. Chrome 85.0.4183.83 (Official Build) (64-bit)]
45+
46+
### Smartphone
47+
<!-- please complete the following information -->
48+
- Device: [e.g. iPhone 6]
49+
- OS: [e.g. iOS 13.6.1]
50+
- Browser: [e.g. Chrome 22]
51+
52+
### Additional context
53+
<!-- Add any other context about the problem here. -->

‎.github/ISSUE_TEMPLATE/feature_request.md

+30
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,30 @@
1+
---
2+
name: Feature Request
3+
about: Suggest an idea for this project
4+
labels: enhancement
5+
---
6+
7+
<!-- Note: Please follow the template to open a new issue, otherwise your question will probably be ignored. -->
8+
9+
## Checklist
10+
<!-- Please complete the following list of tasks, and then check it by change the "[ ]" to "[x]" -->
11+
- [ ] I have read the [contributing guidelines](https://github.com/cotes2020/jekyll-theme-chirpy/blob/master/.github/CONTRIBUTING.md).
12+
- [ ] There are no similar request on existing issues (including closed ones).
13+
- [ ] I have read the [project progress](https://github.com/cotes2020/jekyll-theme-chirpy/projects) and know the current progress of the project.
14+
- [ ] I was in the `master` branch of the latest code.
15+
16+
17+
## Is your feature request related to a problem? Please describe
18+
<!-- A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] -->
19+
20+
21+
## Describe the solution you'd like
22+
<!-- A clear and concise description of what you want to happen. -->
23+
24+
25+
## Describe alternatives you've considered
26+
<!-- A clear and concise description of any alternative solutions or features you've considered. -->
27+
28+
29+
## Additional context
30+
<!-- Add any other context or screenshots about the feature request here. -->

‎.github/ISSUE_TEMPLATE/question.md

+20
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,20 @@
1+
---
2+
name: Question
3+
about: Ask what ever you want
4+
labels: question
5+
---
6+
7+
<!-- Note: Please follow the template to open a new issue, otherwise your question will probably be ignored. -->
8+
9+
## Checklist
10+
11+
<!-- Please complete the following list of tasks, and then check it by change the "[ ]" to "[x]" -->
12+
13+
- [ ] I have read the [tutorials](https://chirpy.cotes.info/categories/tutorial/) and know the correct effect of the functional design.
14+
- [ ] There are no similar question on existing issues (including closed ones).
15+
- [ ] I searched the Internet for related problems, but still couldn't solve it.
16+
- [ ] My question is based on the latest code of `master` branch.
17+
18+
19+
## Description
20+
<!-- Please describe your question. -->

‎.github/PULL_REQUEST_TEMPLATE.md

+44
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,44 @@
1+
## Description
2+
3+
<!--
4+
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
5+
-->
6+
7+
e.g. Fixes #(issue)
8+
9+
## Type of change
10+
11+
<!--
12+
Please select the desired item checkbox and change it to "[x]", then delete options that are not relevant.
13+
-->
14+
- [ ] Bug fix (non-breaking change which fixes an issue)
15+
- [ ] New feature (non-breaking change which adds functionality)
16+
- [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
17+
- [ ] Documentation update
18+
19+
## How has this been tested
20+
21+
<!--
22+
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration
23+
-->
24+
25+
- [ ] I have run `bash ./tools/build.sh && bash ./tools/test.sh` (at the root of the project) locally and passed
26+
- [ ] I have tested this feature in the browser
27+
28+
### Test Configuration
29+
30+
- Browerser type & version:
31+
- Operating system:
32+
- Bundler version:
33+
- Ruby version:
34+
- Jekyll version:
35+
36+
### Checklist
37+
<!-- Select checkboxes by change the "[ ]" to "[x]" -->
38+
- [ ] My code follows the [Google style guidelines](https://google.github.io/styleguide/)
39+
- [ ] I have performed a self-review of my own code
40+
- [ ] I have commented my code, particularly in hard-to-understand areas
41+
- [ ] I have made corresponding changes to the documentation
42+
- [ ] My changes generate no new warnings
43+
- [ ] I have added tests that prove my fix is effective or that my feature works
44+
- [ ] Any dependent changes have been merged and published in downstream modules

‎.github/workflows/ci.yml

+80
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,80 @@
1+
name: 'Continuous Integration'
2+
on:
3+
push:
4+
branches-ignore:
5+
- 'production'
6+
tags-ignore:
7+
- '*'
8+
paths-ignore:
9+
- '.github/**'
10+
- '!.github/workflows/ci.yml'
11+
- '.travis.yml'
12+
- '.gitignore'
13+
- 'docs/**'
14+
- 'README.md'
15+
- 'LICENSE'
16+
pull_request:
17+
paths:
18+
- '**'
19+
20+
jobs:
21+
ci:
22+
runs-on: ${{ matrix.os }}
23+
strategy:
24+
matrix:
25+
os: [ubuntu-latest, macos-latest]
26+
27+
steps:
28+
- uses: actions/setup-ruby@v1
29+
with:
30+
ruby-version: '2.6.x'
31+
32+
- name: Install tools (for Ubuntu)
33+
if: matrix.os == 'ubuntu-latest'
34+
run: |
35+
sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys CC86BB64
36+
sudo add-apt-repository ppa:rmescandon/yq
37+
sudo apt update
38+
sudo apt install yq -y
39+
40+
- name: Install tools (for macOS)
41+
if: matrix.os == 'macos-latest'
42+
run: |
43+
brew install coreutils
44+
brew install yq
45+
46+
- name: Checkout
47+
uses: actions/checkout@v2
48+
with:
49+
fetch-depth: 0
50+
51+
- name: Bundle Caching
52+
id: bundle-cache
53+
uses: actions/cache@v1
54+
with:
55+
path: vendor/bundle
56+
key: ${{ runner.os }}-gems-${{ hashFiles('**/Gemfile') }}
57+
restore-keys: |
58+
${{ runner.os }}-gems-
59+
60+
- name: Bundle config
61+
run: |
62+
bundle config path vendor/bundle
63+
64+
- name: Bundle Install
65+
if: steps.bundle-cache.outputs.cache-hit != 'true'
66+
run: |
67+
bundle install
68+
69+
- name: Bundle Install locally
70+
if: steps.bundle-cache.outputs.cache-hit == 'true'
71+
run: |
72+
bundle install --local
73+
74+
- name: Build Site
75+
run: |
76+
bash tools/build.sh
77+
78+
- name: Test Site
79+
run: |
80+
bash tools/test.sh

‎.github/workflows/issues-cleaner.yml

+24
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,24 @@
1+
name: "Close stale issues"
2+
on:
3+
schedule:
4+
- cron: "0 0 * * *"
5+
6+
jobs:
7+
stale:
8+
runs-on: ubuntu-latest
9+
steps:
10+
- env:
11+
DAYS_TO_STALE: ${{ 5 }}
12+
DAYS_TO_CLOSE: ${{ 2 }}
13+
uses: actions/stale@v3
14+
with:
15+
repo-token: ${{ secrets.GH_PAT }}
16+
stale-issue-message: 'This issue is stale because it has been open ${{ env.DAYS_TO_STALE }} days with no activity. Remove stale label or comment or this will be closed in ${{ env.DAYS_TO_CLOSE }} days'
17+
stale-issue-label: 'stale'
18+
exempt-issue-labels: 'pending, in progress'
19+
stale-pr-message: 'This PR is stale because it has been open ${{ env.DAYS_TO_STALE }} days with no activity. Remove stale label or comment or this will be closed in ${{ env.DAYS_TO_CLOSE }} days'
20+
stale-pr-label: 'stale'
21+
exempt-pr-labels: 'pending, in progress'
22+
days-before-stale: ${{ env.DAYS_TO_STALE }}
23+
days-before-close: ${{ env.DAYS_TO_CLOSE }}
24+
# debug-only: true

‎.github/workflows/issues-filter.yml

+18
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,18 @@
1+
name: "Close Irregular Issues"
2+
3+
on:
4+
issues:
5+
types: [opened, edited]
6+
7+
jobs:
8+
auto_close_issues:
9+
runs-on: ubuntu-latest
10+
steps:
11+
- name: Checkout
12+
uses: actions/checkout@v1
13+
- name: Automatically close issues that don't follow the issue template
14+
uses: lucasbento/[email protected]
15+
with:
16+
github-token: ${{ secrets.GH_PAT }}
17+
issue-close-message: "@${issue.user.login}: hello! :wave:\n\nThis issue is being automatically closed because it does not follow the issue template. \n> Follow the template to edit this issue and it will automatically reopen."
18+
closed-issues-label: "🙁 Not following issue template"

0 commit comments

Comments
 (0)