Can't I apply this method to an existing repository?

[zipidashlim]

Why are you starting this discussion?

Question

What GitHub Actions topic or product is this about?

ARC (Actions Runner Controller)

Discussion Details

제가 이 방법을 기존의 레포지토리에 적용할 순 없나요?
Can't I apply this method to an existing repository?

단도직입적으로.

링크

이 방법을 기존에 만든 레포지토리에 적용할 수는 없나요?

회사 동료분하고 깃허브로 동기화해서 옵시디언 공요하려는데, 잘 모르겠네요.

in a straightforward manner.

Link

Can't I apply this method to the existing repository?

I'm trying to synchronize with my co-worker on GitHub and play Obsidian, but I'm not sure.

그리고 이건 위 링크 번역본 입니다.
And the below is translated version of upper link.
ChatGPT

[Sidopolis]

Yes, you can apply ARC (Actions Runner Controller) to an existing repository, but it depends on how your environment is set up. ARC works at the organization or enterprise level, so the repository just needs to be configured properly to use the self-hosted runners managed by ARC.

• If you’re trying to sync with a co-worker and use it with Obsidian via GitHub, make sure:
• Your repo has the proper workflows configured in .github/workflows/
• Your GitHub organization is already set up with ARC and has available runners
• Your repository is allowed to use those runners (check runner group settings)

It might need a bit of setup, but you don’t need to start a new repo just to use ARC.

[geethasagarb]

Yes, you can apply ARC to an existing repository, but there are a few things to keep in mind:
1. ARC is installed and managed at the organization or enterprise level, not on individual repositories. So instead of modifying a single repo, you’ll deploy ARC to manage runners across multiple repos in your org.
2. Once ARC is set up, you can assign self-hosted runners (managed by ARC) to any existing repo by adding the appropriate runner labels in your GitHub Actions workflow.
3. Make sure you’ve properly configured permissions and namespace access between ARC and your GitHub organization.

If your goal is to sync Obsidian notes via GitHub, ARC might be overkill unless you specifically need scalable, self-hosted runners. A simpler Git-based workflow (e.g., pushing/pulling between a shared private repo) might be more suitable.

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬