starred/crono
1
0
Fork 0
mirror of https://github.com/plashchynski/crono.git synced 2026-01-11 21:10:24 +01:00
Code Issues 35 Packages Projects Releases 9 Wiki Activity

[PR #107] [MERGED] Add GitHub actions for specs #112

New Issue
Closed
opened 2025-12-29 00:22:42 +01:00 by adam · 0 comments
adam commented 2025-12-29 00:22:42 +01:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/plashchynski/crono/pull/107
Author: @mediafinger
Created: 7/8/2022
Status: ✅ Merged
Merged: 7/15/2022
Merged by: @plashchynski

Base: main ← Head: add-github-actions-for-specs

📝 Commits (2)

  • 4abc999 doc: List compatible Ruby versions in the README
  • a421a62 ci: Add GitHub Action to run specs

📊 Changes

3 files changed (+45 additions, -2 deletions)

View changed files

➕ .github/workflows/rspec.yml (+36 -0)
📝 Gemfile.lock (+5 -2)
📝 README.md (+4 -0)

📄 Description

Hello plashchynski thanks for creating and maintaining crono.

When you are open to merging these changes, I might propose a few more, like:

  • add a "how-to update to crono v2.0" to the README (even if it just explicitly states that nothing has to be changed or done)
  • adapt crono to be compatible with Ruby 3.0 (which it currently is not)

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/plashchynski/crono/pull/107 **Author:** [@mediafinger](https://github.com/mediafinger) **Created:** 7/8/2022 **Status:** ✅ Merged **Merged:** 7/15/2022 **Merged by:** [@plashchynski](https://github.com/plashchynski) **Base:** `main` ← **Head:** `add-github-actions-for-specs` --- ### 📝 Commits (2) - [`4abc999`](https://github.com/plashchynski/crono/commit/4abc9995830f5d4634656336d79aa6fe3544ab4c) doc: List compatible Ruby versions in the README - [`a421a62`](https://github.com/plashchynski/crono/commit/a421a6207bbc2892a16a0f25ddd883b057c4163a) ci: Add GitHub Action to run specs ### 📊 Changes **3 files changed** (+45 additions, -2 deletions) <details> <summary>View changed files</summary> ➕ `.github/workflows/rspec.yml` (+36 -0) 📝 `Gemfile.lock` (+5 -2) 📝 `README.md` (+4 -0) </details> ### 📄 Description Hello [plashchynski](https://github.com/plashchynski/crono/commits?author=plashchynski) thanks for creating and maintaining crono. When you are open to merging these changes, I might propose a few more, like: * add a _"how-to update to crono v2.0"_ to the README (even if it just explicitly states that nothing has to be changed or done) * adapt crono to be compatible with Ruby 3.0 (which it currently is not) --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
adam added the pull-request label 2025-12-29 00:22:42 +01:00
adam closed this issue 2025-12-29 00:22:42 +01:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
enhancement
enhancement
pull-request
Mirrored from GitHub Pull Request
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/crono#112
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?