Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

`getNoLanguagesError` / Did not detect any languages to analyze. Please update input in workflow or check that GitHub detects the correct languages in your repository.

Aperta
#2,127 0 commenti 1 reazione 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
35/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Ferma
Stack tecnologico
github-actions, typescript, yaml
Ambito
ci-cd, security

Direzione di ricerca

Inizia con il workflow CodeQL e i log di github/codeql-action/init collegati nelle esecuzioni 7839464145, 7840155320 e 7840157412; confronta il rilevamento dei linguaggi con le diverse autorizzazioni dei fork. Il lavoro è completato quando gli errori relativi a no-language e alle autorizzazioni spiegano chiaramente la loro causa e indirizzano gli utenti alla guida pertinente del workflow o della documentazione.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

I created two forks of https://github.com/octokit/request.js:

  1. https://github.com/jsoref/request.js
  2. https://github.com/check-spelling-sandbox/request.js

both were created at approximately the same time.

Every single run of the codeql workflow in my repository has ❌ failed.

The first three runs ❌ failed in check-spelling-sandbox, but after giving it security-events: write, it would occasionally
✅ succeed -- and it never yielded the output below.

I'm quite confused by the behavior and output of https://github.com/jsoref/request.js/actions/runs/7839464145

To some extent, the commits in my fork are just copies of the commits in the sandbox fork...

Annotations

1 error and 1 warning
CodeQL-Build
Did not detect any languages to analyze. Please update input in workflow or check that GitHub detects the correct languages in your repository.
CodeQL-Build
Debugging artifacts are unavailable since the 'init' Action failed before it could produce any.

https://github.com/jsoref/request.js/actions/runs/7839464145/job/21392525353

Run github/codeql-action/init@v3
Setup CodeQL tools
Validating workflow
Load language configuration
  /opt/hostedtoolcache/CodeQL/2.16.1/x64/codeql/codeql resolve languages --format=json
  {
    "xml" : [
      "/opt/hostedtoolcache/CodeQL/2.16.1/x64/codeql/xml"
    ],
    "javascript" : [
      "/opt/hostedtoolcache/CodeQL/2.16.1/x64/codeql/javascript"
    ],
    "go" : [
      "/opt/hostedtoolcache/CodeQL/2.16.1/x64/codeql/go"
    ],
    "python" : [
      "/opt/hostedtoolcache/CodeQL/2.16.1/x64/codeql/python"
    ],
    "properties" : [
      "/opt/hostedtoolcache/CodeQL/2.16.1/x64/codeql/properties"
    ],
    "ruby" : [
      "/opt/hostedtoolcache/CodeQL/2.16.1/x64/codeql/ruby"
    ],
    "csharp" : [
      "/opt/hostedtoolcache/CodeQL/2.16.1/x64/codeql/csharp"
    ],
    "html" : [
      "/opt/hostedtoolcache/CodeQL/2.16.1/x64/codeql/html"
    ],
    "java" : [
      "/opt/hostedtoolcache/CodeQL/2.16.1/x64/codeql/java"
    ],
    "yaml" : [
      "/opt/hostedtoolcache/CodeQL/2.16.1/x64/codeql/yaml"
    ],
    "swift" : [
      "/opt/hostedtoolcache/CodeQL/2.16.1/x64/codeql/swift"
    ],
    "cpp" : [
      "/opt/hostedtoolcache/CodeQL/2.16.1/x64/codeql/cpp"
    ],
    "csv" : [
      "/opt/hostedtoolcache/CodeQL/2.16.1/x64/codeql/csv"
    ]
  }
  Automatically detected languages: 
  Error: Did not detect any languages to analyze. Please update input in workflow or check that GitHub detects the correct languages in your repository.
-- note that this repository is configured w/ default read&write permissions (I haven't adjusted my forking code to disable actions -- I will probably do that eventually as workflows in my personal account are too dangerous and frustrating).

By contrast, https://github.com/check-spelling-sandbox/request.js/actions/runs/7840155320 fails in a way that I understand (and am working to fix):

Annotations

2 errors and 1 warning
CodeQL-Build
Resource not accessible by integration
CodeQL-Build
Resource not accessible by integration
CodeQL-Build
Debugging artifacts are unavailable since the 'init' Action failed before it could produce any.

And https://github.com/check-spelling-sandbox/request.js/actions/runs/7840157412 passes

Annotations

2 warnings
CodeQL-Build
This run of the CodeQL Action does not have permission to access Code Scanning API endpoints. As a result, it will not be opted into any experimental features. This could be because the Action is running on a pull request from a fork. If not, please ensure the Action has the 'security-events: write' permission. Details: Resource not accessible by integration
CodeQL-Build
Feature flags do not specify a default CLI version. Falling back to the CLI version shipped with the Action. This is 2.16.1.

-- for the record, the check-spelling-sandbox org uses https://docs.github.com/en/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization#setting-the-permissions-of-the-github_token-for-your-organization to restrict permissions to read -- eventually I'll file a PR to improve the message here since it should be aware that this is a possibility.


Isn't this all the same code? Why would one of my forks complain about not being able to guess what file types are involved while another is able to?

Ideally the error reporting should be sufficiently clear that a non expert would be able to understand what to do. If the possible actions necessary to resolve the problem are sufficiently complicated, then it'd be a good idea to linking to a document that can walk users through the possibilities.

Lingua principale
TypeScript
Stelle
1.6k
Fork
493
Merge medio
1g 13h
PR unite (30g)
44

Guida per i contributori

Apri la guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di github/codeql-action

Tutte le issue di github/codeql-action

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.