Skip to content

GitHub Action to read .env file and add variables to GITHUB_ENV

active 2023-09-182026-05-13 (UTC)

Complete coverage26,667 / 26,667 hourly files (100%) · 2 absent upstream2023-08-152026-08-30 (UTC)
Events
61
Pushes
5
Pull requests
1
Issues
11
Stars
25
Forks
6

Activity over time

Daily event counts in the loaded window

Line chart, 969 days from 2023-09-18 to 2026-05-13. Pushes: 5 total, peak 2 in a day. Pull requests: 1 total, peak 1 in a day. Issues: 11 total, peak 3 in a day. Comments: 11 total, peak 4 in a day. Stars: 25 total, peak 2 in a day.

  • Pushes
  • Pull requests
  • Issues
  • Comments
  • Stars

Stars, PRs, issues and forks are under-captured in the later part of this window. GH Archive progressively stopped capturing non-push events during 2026 — −95% or worse by the end of the window. Every series here except Pushes fades for that reason, so a decline above reflects the archive, not this repository. Pushes stay reliable throughout, so read them, and the contributor counts derived from them, as the real signal. Data health has the measurements.

Top contributors

Pushes, PRs, issues, reviews and comments — stars and forks excluded, so this is contribution rather than popularity

ContributorContributionsPushesPRsComments
xom9ikk15505
Nasfame3001
BillyTom3002
ogarcia2001
pritster52001
Dogacel1000
gravelg1010
rkrisztian1001

Recent activity

Latest issues, pull requests and releases

  • Issue#23Dogacel2024-06-05 13:41
    [Bug] Can't override existing value, behavior changed after `dotenv-expand`.
  • Issue comment#22ogarcia2024-06-03 14:44
    Something strange happens with the upgrade to Node 20
  • Issue comment#9xom9ikk2024-05-31 22:11
    FEATURE REQUEST : ABILITY TO PARSE ENV FROM DIFFERENT REPO
  • Issue#9xom9ikk2024-05-31 22:11
    FEATURE REQUEST : ABILITY TO PARSE ENV FROM DIFFERENT REPO
  • Issue comment#17xom9ikk2024-05-31 22:08
    Question: Does this action need to be added to every job in a workflow.yml file?
  • Issue#17xom9ikk2024-05-31 22:08
    Question: Does this action need to be added to every job in a workflow.yml file?
  • Issue comment#22xom9ikk2024-05-31 22:06
    Something strange happens with the upgrade to Node 20
  • Issue#22xom9ikk2024-05-31 22:06
    Something strange happens with the upgrade to Node 20
  • Issue#22ogarcia2024-05-19 10:47
    Something strange happens with the upgrade to Node 20
  • Issue comment#20BillyTom2024-03-08 13:42
    Please update to Node 20
  • Issue#6xom9ikk2024-03-08 12:10
    Use the tag `v1` as an alias to the latest version 1
  • Issue comment#21xom9ikk2024-03-08 12:08
    chore: upgrade to node 20
  • Issue comment#20xom9ikk2024-03-08 12:06
    Please update to Node 20
  • Releasexom9ikk2024-03-08 12:06
    Bump node version to 20
  • Issue#20xom9ikk2024-03-08 12:01
    Please update to Node 20
  • Issue comment#21BillyTom2024-03-08 11:05
    chore: upgrade to node 20
  • Pull request#21gravelg2024-02-27 16:17
  • Issue#20BillyTom2024-02-14 08:46
    Please update to Node 20
  • Issue#19Nasfame2023-10-27 14:11
    chore: update doc
  • Issue comment#18Nasfame2023-10-27 14:07
    proposal: v3
  • Issue#18Nasfame2023-10-27 14:06
    proposal: v3
  • Issue#17pritster52023-10-13 00:50
    Question: Does this action need to be added to every job in a workflow.yml file?
  • Issue comment#2pritster52023-10-12 19:14
    ENOENT: no such file or directory, open '.env'
  • Issue comment#5rkrisztian2023-09-18 11:19
    Multiline support

Totals cover only the window loaded into ClickHouse and count events, not GitHub's lifetime totals — 25 stars here means stars gained during the window, not the repo's star count.