- Berlin, Germany
- @devnullcake
Highlights
- 22 discussions answered
Block or Report
Block or report abn
Report abuse
Contact GitHub support about this user’s behavior. Learn more about reporting abuse.
Report abusePinned
-
-
aiographql-client Public
An asynchronous GraphQL client built on top of aiohttp and graphql-core-next
-
-
-
-
1
# RPM Build Flow23This document details a simple RPM build flow pattern used to build and host RPM artifacts for open source projects. The below is a visual summary of this flow.
4<img src="https://gist.githubusercontent.com/abn/daf262e7e454509df1429c87068923d1/raw/rpm-build-workflow.png" />
5
741 contributions in the last year
Activity overview
Contributed to
python-poetry/poetry,
python-poetry/poetry-core,
abn/aiographql-client
and 39 other
repositories
Contribution activity
May 2022
Created 36 commits in 4 repositories
Created 1 repository
- abn/detectron2 Python
Created a pull request in python-poetry/poetry that received 5 comments
Opened 27 other pull requests in 4 repositories
python-poetry/poetry
19
merged
1
closed
-
config: introduce
installer.no-binary - ci: allow doc builds from forks
- info: cache get metadata from pep517
- install: add --no-binary option
- ci: preview doc changes
- ci: preview doc changes
- ensure setup.py editable builds do not use pep517
- improve git http authentication via repository configuration
- tests: make test compatible with core > 1.1.0a7
- docs: add information on git and http-basic auth
- docs: remove ambiguity about pep440 and semver
- update locked dependencies
- doc: fix link typo in repositories
- git: allow http auth via dulwich
- doc: improve repository documentation
- repos: configure source for credential lookup
- factory: reuse dependency specification utils
- refactor dependency specification parsing logic
- vcs/git: improve logging for issue debugging
- fix dataclass InitVar usage for git backend
python-poetry/poetry-core
1
open
3
merged
python-poetry/website
2
merged
facebookresearch/detectron2
1
closed
Reviewed 41 pull requests in 3 repositories
python-poetry/poetry
25 pull requests
- [document] Mention poetry.toml
- Add --dry-run option to version command
- Update repositories.md
-
replace
poetry plugincommands with more genericpoetry selfcommands - Lazy load credentials for legacy repositories
- ci: preview doc changes
- build.script: use build environment for execution
- tests: make tests compatible with core > 1.1.0a7
- Update documents
- improve git http authentication via repository configuration
-
add
--whyoption topoetry show - [pre-commit.ci] pre-commit autoupdate
-
Use env vars if either
--usernameor--password(or both) is missing - chore(inspection): remove type errors
-
Replace
python-check-blanket-type-ignorewithignore-without-codeinmypy - doc: improve repository documentation
- tests/helpers: restore symlink fallback on Windows…
- remove pipenv comparison
- Canonicalized names
- git: allow http auth via dulwich
- Feat: Added option to disable SSL verify
- factory: reuse dependency specification utils
- factory: cleanup creation from package
- Replace poetry.utils.appdirs with platformdirs
- Fix flicker when displaying executor operations
- Some pull request reviews not shown.
python-poetry/poetry-core
12 pull requests
- typechecking semver.version_union
- markers: fix union of multi markers if one marker is a subset of the other marker
- version: fix normalize_version() according to PEP440
- Fix for git subdirectories
- canonicalize package name correctly
- Fix get_python_constraint_from_marker
- typechecking poetry.core.masonry
- Fix stub-only partial namespace packages not recognized as packages
- semver/pep508: handle wildcard exclusions
- support indexed legacy repositories
- utils.link: add PEP 658 (metadata) support
- semver: improve constraint parsing
python-poetry/poetry-plugin-export
2 pull requests
Created an issue in python-poetry/poetry that received 8 comments
ci: come up with a better solution for skipping required checks
Today, we use a skip workflow to skip running test for doc/cirrus only changes. This is because we path-ignore test suite runs for doc only changes…
8
comments

