Skip to content

Preparation resources for the GitHub Actions certification

active 2024-05-252024-05-31 (UTC)

Complete coverage26,769 / 26,769 hourly files (100%) · 2 absent upstream2023-08-152026-09-03 (UTC)
Events
235
Pushes
23
Pull requests
1
Issues
137
Stars
0
Forks
0

Activity over time

Daily event counts in the loaded window

Line chart, 7 days from 2024-05-25 to 2024-05-31. Pushes: 23 total, peak 11 in a day. Pull requests: 1 total, peak 1 in a day. Issues: 137 total, peak 76 in a day. Comments: 71 total, peak 37 in a day. Stars: 0 total, peak 0 in a day.

  • Pushes
  • Pull requests
  • Issues
  • Comments
  • Stars

Top contributors

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

ContributorContributionsPushesPRsComments
lfarci23021171
github-actions[bot]2200

Recent activity

Latest issues, pull requests and releases

  • Issue#65lfarci2024-05-31 06:35
    Explain the difference between GitHub-hosted and self-hosted runners
  • Issue#62lfarci2024-05-31 06:34
    Configure organizational use policies for GitHub Actions
  • Issue comment#62lfarci2024-05-31 06:32
    Configure organizational use policies for GitHub Actions
  • Issue comment#61lfarci2024-05-31 06:29
    Define how to control access to actions within the enterprise
  • Issue#61lfarci2024-05-31 06:29
    Define how to control access to actions within the enterprise
  • Issue#59lfarci2024-05-31 06:24
    Define an approach for managing and leveraging reusable components (i.e. repos for storage, naming conventions for files/folders, and plans for ongoing maintenance)
  • Issue comment#59lfarci2024-05-31 06:24
    Define an approach for managing and leveraging reusable components (i.e. repos for storage, naming conventions for files/folders, and plans for ongoing maintenance)
  • Issue comment#60lfarci2024-05-31 06:23
    Define how to distribute actions for an enterprise
  • Issue#60lfarci2024-05-31 06:23
    Define how to distribute actions for an enterprise
  • Issue comment#58lfarci2024-05-31 06:18
    Explain reuse templates for actions and workflows
  • Issue#58lfarci2024-05-31 06:18
    Explain reuse templates for actions and workflows
  • Issue#72lfarci2024-05-31 06:00
    Explain how to manage repository-level encrypted secrets
  • Issue comment#71lfarci2024-05-31 05:59
    Explain how to manage organization-level encrypted secrets
  • Issue#71lfarci2024-05-31 05:55
    Explain how to manage organization-level encrypted secrets
  • Issue comment#71lfarci2024-05-31 05:52
    Explain how to manage organization-level encrypted secrets
  • Issue#70lfarci2024-05-31 05:51
    Demonstrate how to access encrypted secrets within actions and workflows
  • Issue comment#70lfarci2024-05-31 05:50
    Demonstrate how to access encrypted secrets within actions and workflows
  • Issue comment#70lfarci2024-05-31 05:50
    Demonstrate how to access encrypted secrets within actions and workflows
  • Issue comment#69lfarci2024-05-31 05:41
    Identify the scope of encrypted secrets
  • Issue#69lfarci2024-05-31 05:41
    Identify the scope of encrypted secrets
  • Issue comment#69lfarci2024-05-31 05:40
    Identify the scope of encrypted secrets
  • Issue comment#40lfarci2024-05-30 22:38
    Demonstrate the correct syntax for passing custom environment variables in a workflow step
  • Issue#40lfarci2024-05-30 22:38
    Demonstrate the correct syntax for passing custom environment variables in a workflow step
  • Issue comment#39lfarci2024-05-30 22:37
    Demonstrate how to use default environment variables in a workflow
  • Issue comment#39lfarci2024-05-30 22:36
    Demonstrate how to use default environment variables in a workflow

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