[PR #4304] Add Living in Korea #61409

New Issue

GiteaMirror · 2026-07-12T01:51:27-05:00

GiteaMirror commented

2026-07-12 01:51:27 -05:00

📋 Pull Request Information

Original PR: https://github.com/sindresorhus/awesome/pull/4304
Author: @hwajongpark
Created: 7/2/2026
Status: 🔄 Open

Base: main ← Head: add-living-in-korea

📝 Commits (1)

06e8482 Add Living in Korea

📊 Changes

1 file changed (+1 additions, -0 deletions)

View changed files

📝 readme.md (+1 -0)

📄 Description

List URL: https://github.com/seoulstart/awesome-living-in-korea#readme

What it is and why it should be included:

A curated list of the resources a foreigner actually needs to live in South Korea: government portals, community hubs, everyday apps, and guides across visas, housing, healthcare, taxes, work, and culture. Korea has roughly 3 million foreign residents, and the information they need is scattered across cold government portals, outdated blog posts, and closed Facebook groups. This list pulls the reliable primary sources into one place, organized in the order people actually hit these problems (arrival, then visas, then housing, and so on). The README also has 21 language editions so non-English speakers can use it.

Disclosure: I maintain this as part of Seoulstart, a multilingual guide site for foreign residents in Korea. Seoulstart's own guides appear where they add plain-language depth, but they sit alongside official and community sources (about a third of the entries) and are never presented as the only option.

I reviewed 4 open pull requests with substantive comments (not approvals):

https://github.com/sindresorhus/awesome/pull/4265 (flagged a Web3/Blockchain section that violates the no-blockchain rule, plus vendor-tagline descriptions)
https://github.com/sindresorhus/awesome/pull/4262 (entry describes the list rather than the topic; several entries are not SRE agents)
https://github.com/sindresorhus/awesome/pull/4222 (machine-generated Themes Index section and a duplicated heading anchor)
https://github.com/sindresorhus/awesome/pull/4216 (list is exhaustive rather than curated, with stale and overlapping vendor SKUs)

By submitting this pull request I confirm I've read and complied with the below requirements 🖖

Requirements for your pull request

Fully AI-generated pull requests are not accepted.
Don't open a Draft / WIP pull request while you work on the guidelines.
Don't waste my time. Do a good job, adhere to all the guidelines, and be responsive.
You have to review at least 4 other open pull requests. (Reviewed: #4265, #4262, #4222, #4216, listed above.)
You have read and understood the instructions for creating a list.
This pull request has a title in the format Add Name of List. It should not contain the word Awesome.
Your entry here should include a short description of the project/theme of the list. It should not describe the list itself.
Your entry should be added at the bottom of the appropriate category.
The title of your entry should be title-cased and the URL to your list should end in #readme.
No blockchain-related lists.
The suggested Awesome list complies with the below requirements.

Requirements for your Awesome list

Has been around for at least 30 days.
Is not AI-generated.
Run awesome-lint on your list and fix the reported issues.
The default branch should be named main, not master.
Includes a succinct description of the project/theme at the top of the readme.
It's the result of hard work and the best I could possibly produce.
The repo name of your list should be in lowercase slug format: awesome-name-of-list.
The heading title of your list should be in title case format: # Awesome Name of List.
Non-generated Markdown file in a GitHub repo.
The repo should have awesome-list & awesome as GitHub topics.
Not a duplicate. Please search for existing submissions.
Only has awesome items. Awesome lists are curations of the best, not everything.
Does not contain items that are unmaintained, has archived repo, deprecated, or missing docs.
Includes a project logo/illustration whenever possible.
Entries have a description, unless the title is descriptive enough by itself.
Includes the Awesome badge.
Has a Table of Contents section.
Has an appropriate license.
Has contribution guidelines.
All non-important but necessary content is grouped in a Footnotes section at the bottom of the readme.
Has consistent formatting and proper spelling/grammar.
Does not use hard-wrapping.
Does not include a CI (e.g. GitHub Actions) badge.
Does not include an Inspired by awesome-foo or Inspired by the Awesome project kinda link at the top of the readme.

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/sindresorhus/awesome/pull/4304 **Author:** [@hwajongpark](https://github.com/hwajongpark) **Created:** 7/2/2026 **Status:** 🔄 Open **Base:** `main` ← **Head:** `add-living-in-korea` --- ### 📝 Commits (1) - [`06e8482`](https://github.com/sindresorhus/awesome/commit/06e8482ec864d7615bb1cc9b769178e4dec2a5b6) Add Living in Korea ### 📊 Changes **1 file changed** (+1 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `readme.md` (+1 -0) </details> ### 📄 Description **List URL:** https://github.com/seoulstart/awesome-living-in-korea#readme **What it is and why it should be included:** A curated list of the resources a foreigner actually needs to live in South Korea: government portals, community hubs, everyday apps, and guides across visas, housing, healthcare, taxes, work, and culture. Korea has roughly 3 million foreign residents, and the information they need is scattered across cold government portals, outdated blog posts, and closed Facebook groups. This list pulls the reliable primary sources into one place, organized in the order people actually hit these problems (arrival, then visas, then housing, and so on). The README also has 21 language editions so non-English speakers can use it. Disclosure: I maintain this as part of Seoulstart, a multilingual guide site for foreign residents in Korea. Seoulstart's own guides appear where they add plain-language depth, but they sit alongside official and community sources (about a third of the entries) and are never presented as the only option. I reviewed 4 open pull requests with substantive comments (not approvals): - https://github.com/sindresorhus/awesome/pull/4265 (flagged a Web3/Blockchain section that violates the no-blockchain rule, plus vendor-tagline descriptions) - https://github.com/sindresorhus/awesome/pull/4262 (entry describes the list rather than the topic; several entries are not SRE agents) - https://github.com/sindresorhus/awesome/pull/4222 (machine-generated Themes Index section and a duplicated heading anchor) - https://github.com/sindresorhus/awesome/pull/4216 (list is exhaustive rather than curated, with stale and overlapping vendor SKUs) ### By submitting this pull request I confirm I've read and complied with the below requirements 🖖 ## Requirements for your pull request - [x] Fully AI-generated pull requests are not accepted. - [x] Don't open a Draft / WIP pull request while you work on the guidelines. - [x] **Don't waste my time.** Do a good job, adhere to all the guidelines, and be responsive. - [x] **You have to review at least 4 other [open pull requests](https://github.com/sindresorhus/awesome/pulls?q=is%3Apr+is%3Aopen).** (Reviewed: #4265, #4262, #4222, #4216, listed above.) - [x] You have read and understood the [instructions for creating a list](https://github.com/sindresorhus/awesome/blob/main/create-list.md). - [x] This pull request has a title in the format `Add Name of List`. It should not contain the word `Awesome`. - [x] Your entry here should include a short description of the project/theme of the list. It should not describe the list itself. - [x] Your entry should be added at the bottom of the appropriate category. - [x] The title of your entry should be title-cased and the URL to your list should end in `#readme`. - [x] No blockchain-related lists. - [x] The suggested Awesome list complies with the below requirements. ## Requirements for your Awesome list - [x] **Has been around for at least 30 days.** - [x] Is not AI-generated. - [x] Run [`awesome-lint`](https://github.com/sindresorhus/awesome-lint) on your list and fix the reported issues. - [x] The default branch should be named `main`, not `master`. - [x] **Includes a succinct description of the project/theme at the top of the readme.** - [x] It's the result of hard work and the best I could possibly produce. - [x] The repo name of your list should be in lowercase slug format: `awesome-name-of-list`. - [x] The heading title of your list should be in title case format: `# Awesome Name of List`. - [x] Non-generated Markdown file in a GitHub repo. - [x] The repo should have `awesome-list` & `awesome` as GitHub topics. - [x] Not a duplicate. Please search for existing submissions. - [x] Only has awesome items. Awesome lists are curations of the best, not everything. - [x] Does not contain items that are unmaintained, has archived repo, deprecated, or missing docs. - [x] Includes a project logo/illustration whenever possible. - [x] Entries have a description, unless the title is descriptive enough by itself. - [x] Includes the [Awesome badge](https://github.com/sindresorhus/awesome/blob/main/awesome.md#awesome-badge). - [x] Has a Table of Contents section. - [x] Has an appropriate license. - [x] Has [contribution guidelines](https://github.com/sindresorhus/awesome/blob/main/awesome.md#include-contribution-guidelines). - [x] All non-important but necessary content is grouped in a `Footnotes` section at the bottom of the readme. - [x] Has consistent formatting and proper spelling/grammar. - [x] Does not use hard-wrapping. - [x] Does not include a CI (e.g. GitHub Actions) badge. - [x] Does not include an `Inspired by awesome-foo` or `Inspired by the Awesome project` kinda link at the top of the readme. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

GiteaMirror added the pull-request label 2026-07-12 01:51:27 -05:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/awesome-sindresorhus#61409