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

app_installations reports an error on every repo or suborg change when the plugin is not configured

Open Beginner friendly
#1,111 0 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
64/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
javascript
Domain
backend

Research direction

Start in lib/settings.js, where syncSelectedRepos calls syncAppInstallations whenever hasChangedConfigs is true, and find the point where the enterprise-authenticated client is required. Add a guard so the plugin returns early when no app_installations config exists at the org, suborg, or repo level, even if repos changed. Done means a PR or push that touches a repo file with no enterprise installation and no app_installations config concludes successfully, and the existing config-present path still works.

Written by the indexing model from the issue text.

Description

Version: 3.0.0

syncSelectedRepos always calls syncAppInstallations with the changed repos (lib/settings.js). Because hasChangedConfigs is true, the "No app_installations config found, skipping" early return never applies. Without an enterprise installation, every PR or push that touches a repo file fails with:

Cannot sync app installations: enterprise-authenticated client not available for '<enterprise>'.

This happens even when no app_installations config exists at any level. Settings are still applied, but the check run concludes failure.

Expected: skip the plugin when no app_installations is configured at the org, suborg, or repo level, even when repos changed.

Workaround: add disable_plugins: [app_installations] to deployment-settings.yml.

Dominant language
JavaScript
Stars
924
Forks
227
Avg merge
6h 8m
Merged PRs (30d)
15

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

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 github-community-projects/safe-settings

All issues in github-community-projects/safe-settings

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.