Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[LOGO] black arch

Open Beginner friendly
  • Is something wrong?
#2,369 2 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
68/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
c
Domain
cli

Research direction

Search the existing distro logo definitions and compare their structure with the Arch Linux ASCII art, color codes, and image reference in this issue. Add the black Arch logo following the repository's established format; it is done when the logo appears correctly in the CLI and satisfies the listed size, padding, and color checklist.

Written by the indexing model from the issue text.

Description

logo request
OS

NAME="Arch Linux"
PRETTY_NAME="Arch Linux"
ID=arch
BUILD_ID=rolling
ANSI_COLOR="38;2;23;147;209"
HOME_URL="https://archlinux.org/"
DOCUMENTATION_URL="https://wiki.archlinux.org/"
SUPPORT_URL="https://bbs.archlinux.org/"
BUG_REPORT_URL="https://gitlab.archlinux.org/groups/archlinux/-/issues"
PRIVACY_POLICY_URL="https://terms.archlinux.org/docs/privacy-policy/"
LOGO=archlinux-logo

Distro Website

https://archlinux.org/

ASCII Art
$2        φ
        |
       _⏊_
$1       /$2|$1\
      / $2|$1 \
     _\ $2|$1  \
    /   $2|$1   \
   /   _$2|$1_   \
  /   / $2|$1 \  /_
 /   _\ $2|$1 /_   \
/_―'⎺   $2|$1   ⎺'―_\
        $2|

"color": {
    "1": "38;2;155;0;0",
    "2": "38;2;128;128;128"
}
Image
Original Image URL

https://blackarch.ru/wp-content/uploads/2016/01/ba-logo.png

Checklist
  • The ASCII art is smaller than 50x20 characters (W x H).
  • The ASCII art includes color codes, or the color codes are available in os-release.
  • The ASCII art has no internal padding (spaces at the start and/or end of lines).
Dominant language
C
Stars
24.8k
Forks
908
Avg merge
14h 57m
Merged PRs (30d)
19

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from fastfetch-cli/fastfetch

All issues in fastfetch-cli/fastfetch

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.