Skip to content

contentstack/contentstack-repeatable-releases-scheduling

View on GitHub ↗Related repositories →

You can use Contentstack with AWS Lambda to create useful automated systems. They can be combined to automate the process of creating and deploying releases in Contentstack. This eliminates the need of creating releases manually. You simply need to add your items to the release and they will get deployed on the specified environment at the scheduled time (specified through the script)

active 2023-09-05 → 2025-12-18 (UTC)

Complete coverage27,344 / 27,344 hourly files (100%) · 2 absent upstream2023-08-15 → 2026-09-27 (UTC)
Events
43
Pushes
34
Pull requests
4
Issues
0
Stars
0
Forks
0

Activity over time

Daily event counts in the loaded window

Line chart, 836 days from 2023-09-05 to 2025-12-18. Pushes: 34 total, peak 6 in a day. Pull requests: 4 total, peak 2 in a day. Issues: 0 total, peak 0 in a day. Comments: 0 total, peak 0 in a day. Stars: 0 total, peak 0 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
aravindbuilt323110
contentstack-admin6330
abhishek3051000

Recent activity

Latest issues, pull requests and releases

  • Pull request#16aravindbuilt2024-04-15 22:36
  • Pull request#15contentstack-admin2024-04-15 21:26
  • Pull request#14contentstack-admin2024-02-02 23:32
  • Pull request#13contentstack-admin2024-02-02 16:43

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.