maint: arch linux repository publication / distrobution for all contributors
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 30/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Active
- Tech stack
- javascript
- Domain
- release
Research direction
Start by reading the README entry for the Arch Linux package and inspect the linked AUR package page to understand how it is currently published. Then investigate whether publication can be automated through npm or GitHub Actions. Done means documenting or implementing a clear publication workflow; the issue does not specify which outcome is wanted.
Written by the indexing model from the issue text.
Description
On our readme file i noticed that there is a arch linux distribution that must have separate access
See here.
https://aur.archlinux.org/packages/all-contributors-cli
I do not know how this package was published previously to that repository. if anyone happens to know what that workflow looks like (ie can we automate it via npm or otherwise via github?) i'd love any insight!!
- Dominant language
- JavaScript
- Stars
- 424
- Forks
- 151
- Avg merge
- 2d 1h
- Merged PRs (30d)
- 15
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from all-contributors/cli
-
Unquoted commit message is causing `npx all-contributors add` to fail on v7.0.0Possibly taken @stchigel claimed this 1 day ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
all-contributors/cli#587 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
all-contributors/cli#586 ·
Maintainers usually reply within 1 day
-
[BUG]: Markdown provided in `types[key].link` is injected as-is into HTMLAnchorElement's href attributePossibly taken @theworker02 claimed this 34 days ago. Open
Difficulty 3/5 1-2 days Newbie friendliness 61/100
all-contributors/cli#520 · 1 comment ·
Maintainers usually reply within 1 day
-
Additional Config File OptionsMay be free again A pull request for this issue was closed without being merged. Open
Difficulty 3/5 1-2 days Newbie friendliness 68/100
all-contributors/cli#499 · 2 comments · 6 reactions ·
Maintainers usually reply within 1 day
-
Consider adding a PR title checker to enforce angular / conventional commitsMay be free again A pull request for this issue was closed without being merged. Opentype: ci type: enhancement type: infrastructure
Difficulty 2/5 1-3 hours Newbie friendliness 42/100
all-contributors/cli#482 · 3 comments · 1 reaction ·
Maintainers usually reply within 1 day
All issues in all-contributors/cli
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
check:failed logos:add
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
iptv-org/database#38874 · 1 comment ·
Maintainers usually reply within 4 days
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
githubnext/gh-aw-workshop#5193 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100