Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
60 changes: 30 additions & 30 deletions .github/ISSUE_TEMPLATE/bug.yml
Original file line number Diff line number Diff line change
Expand Up @@ -2,35 +2,35 @@ name: Bug report
description: Submit a bug report
labels: ["bug"]
body:
- type: textarea
attributes:
label: "Problem:"
description: >
Give a clear description on what's going wrong and how to reproduce it, if possible.
- type: textarea
attributes:
label: "Problem:"
description: >
Give a clear description on what's going wrong and how to reproduce it, if possible.

This should only be for *bugs*, not crashes. For that, use the crash template.
This should only be for *bugs*, not crashes. For that, use the crash template.

value: |
```c
// Add your code here, if needed
```
validations:
required: true
- type: input
attributes:
label: "Version:"
value: |
What version(s) of PyAwaitable are you using?
validations:
required: true
- type: dropdown
attributes:
label: "Operating system(s) tested on:"
multiple: true
options:
- Linux
- macOS
- Windows
- Other
validations:
required: false
value: |
```c
// Add your code here, if needed
```
validations:
required: true
- type: input
attributes:
label: "Version:"
value: |
What version(s) of PyAwaitable are you using?
validations:
required: true
- type: dropdown
attributes:
label: "Operating system(s) tested on:"
multiple: true
options:
- Linux
- macOS
- Windows
- Other
validations:
required: false
60 changes: 30 additions & 30 deletions .github/ISSUE_TEMPLATE/crash.yml
Original file line number Diff line number Diff line change
Expand Up @@ -2,35 +2,35 @@ name: Crash report
description: Submit a crash report
labels: ["crash"]
body:
- type: textarea
attributes:
label: "Crash Information:"
description: >
Give a clear description of what happened and how to reproduce it, if possible. If you aren't sure, attempt to run the program through a debugger, such as [Valgrind](https://valgrind.org/) or enabling [faulthandler](https://docs.python.org/3/library/faulthandler.html).
- type: textarea
attributes:
label: "Crash Information:"
description: >
Give a clear description of what happened and how to reproduce it, if possible. If you aren't sure, attempt to run the program through a debugger, such as [Valgrind](https://valgrind.org/) or enabling [faulthandler](https://docs.python.org/3/library/faulthandler.html).

This should only be for *crashes* not bugs. For that, use the bug template.
This should only be for *crashes* not bugs. For that, use the bug template.

value: |
```c
// Add your code here, if needed
```
validations:
required: true
- type: input
attributes:
label: "Version:"
value: |
What version(s) of PyAwaitable are you using?
validations:
required: true
- type: dropdown
attributes:
label: "Operating system(s) tested on:"
multiple: true
options:
- Linux
- macOS
- Windows
- Other
validations:
required: false
value: |
```c
// Add your code here, if needed
```
validations:
required: true
- type: input
attributes:
label: "Version:"
value: |
What version(s) of PyAwaitable are you using?
validations:
required: true
- type: dropdown
attributes:
label: "Operating system(s) tested on:"
multiple: true
options:
- Linux
- macOS
- Windows
- Other
validations:
required: false
32 changes: 16 additions & 16 deletions .github/ISSUE_TEMPLATE/feature.yml
Original file line number Diff line number Diff line change
Expand Up @@ -2,20 +2,20 @@ name: Feature
description: Suggest a new feature.
labels: ["feature"]
body:
- type: markdown
attributes:
value: |
# Feature Proposal
- type: markdown
attributes:
value: |
# Feature Proposal

This is where you should propose a *new* feature to PyAwaitable. New features should not make breaking changes. This should be for something totally new, such as adding a new function to the ABI. General improvements to existing features should be made using an improvement request.
- type: textarea
attributes:
label: "Proposal:"
description: >
Outline your idea and why it would be a good idea for PyAwaitable. Make sure to include an example API for what this could look like if implemented.
value: |
```c
// Example API
```
validations:
required: true
This is where you should propose a *new* feature to PyAwaitable. New features should not make breaking changes. This should be for something totally new, such as adding a new function to the ABI. General improvements to existing features should be made using an improvement request.
- type: textarea
attributes:
label: "Proposal:"
description: >
Outline your idea and why it would be a good idea for PyAwaitable. Make sure to include an example API for what this could look like if implemented.
value: |
```c
// Example API
```
validations:
required: true
32 changes: 16 additions & 16 deletions .github/ISSUE_TEMPLATE/improvement.yml
Original file line number Diff line number Diff line change
Expand Up @@ -2,20 +2,20 @@ name: Improvement
description: Suggest an improvement to an existing feature.
labels: ["improvement"]
body:
- type: markdown
attributes:
value: |
# Improvement
- type: markdown
attributes:
value: |
# Improvement

An improvement proposal should be related to an *existing* feature. For example, adding some functionality to the *existing* coroutine implementation.
- type: textarea
attributes:
label: "Description:"
description: >
Outline what needs to be improved and why? Be sure to include an example API if necessary.
value: |
```c
// Example API
```
validations:
required: true
An improvement proposal should be related to an *existing* feature. For example, adding some functionality to the *existing* coroutine implementation.
- type: textarea
attributes:
label: "Description:"
description: >
Outline what needs to be improved and why? Be sure to include an example API if necessary.
value: |
```c
// Example API
```
validations:
required: true
104 changes: 52 additions & 52 deletions .github/workflows/build.yml
Original file line number Diff line number Diff line change
@@ -1,59 +1,59 @@
name: Build

on:
push:
tags:
- v*
branches:
- master
paths:
- 'src/**'
pull_request:
branches:
- master
push:
tags:
- v*
branches:
- master
paths:
- "src/**"
pull_request:
branches:
- master

concurrency:
group: build-${{ github.head_ref }}
cancel-in-progress: true
group: build-${{ github.head_ref }}
cancel-in-progress: true

jobs:
pure-python-wheel-and-sdist:
name: Build a pure Python wheel and source distribution
runs-on: ubuntu-latest

steps:
- uses: actions/checkout@v3
with:
fetch-depth: 0

- name: Install build dependencies
run: python -m pip install --upgrade build

- name: Build
run: python -m build

- uses: actions/upload-artifact@v4
with:
name: artifacts
path: dist/*
if-no-files-found: error

publish:
name: Publish release
needs:
- pure-python-wheel-and-sdist
runs-on: ubuntu-latest
if: github.event_name == 'push' && startsWith(github.event.ref, 'refs/tags')

steps:
- uses: actions/download-artifact@v4
with:
name: artifacts
path: dist

- name: Push build artifacts to PyPI
uses: pypa/[email protected]
with:
skip_existing: true
user: __token__
password: ${{ secrets.PYPI_API_TOKEN }}
pure-python-wheel-and-sdist:
name: Build a pure Python wheel and source distribution
runs-on: ubuntu-latest

steps:
- uses: actions/checkout@v3
with:
fetch-depth: 0

- name: Install build dependencies
run: python -m pip install --upgrade build

- name: Build
run: python -m build

- uses: actions/upload-artifact@v4
with:
name: artifacts
path: dist/*
if-no-files-found: error

publish:
name: Publish release
needs:
- pure-python-wheel-and-sdist
runs-on: ubuntu-latest
if: github.event_name == 'push' && startsWith(github.event.ref, 'refs/tags')

steps:
- uses: actions/download-artifact@v4
with:
name: artifacts
path: dist

- name: Push build artifacts to PyPI
uses: pypa/[email protected]
with:
skip_existing: true
user: __token__
password: ${{ secrets.PYPI_API_TOKEN }}
Loading
Loading