✨ New Smart Github Action: replicator

[arcane-engine]

I've successfully created the new Smart Github Action named "replicator" as per your request. Here's what has been done:

1. Action Metadata File (action.yaml): A new action metadata file for "replicator" has been created, defining the necessary inputs such as template-path, result-path, and characteristics for the action to function.

2. Action Code File (replicator.py): The Python script for the "replicator" action has been set up. It's designed to read the specified template, create a new file or code snippet based on the characteristics provided, and save it at the specified result path.

3. Workflow File (replicator.yaml): A new workflow has been added to the .github/workflows directory, allowing the action to be triggered manually (workflow_dispatch). This workflow requires inputs for the template path, result path, and characteristics of the result, aligning with the action's design.

These components together fulfill the task description you provided, enabling the creation of new files or code snippets based on existing templates with specified characteristics.

[arcane-engine]

Looks good to me

[mlamina]

/pilot look at commit-monitor/README.md and make sure there is an equivalent replicator/README.md

[arcane-engine]

I've checked and found that there wasn't an equivalent README.md for the replicator action. I've now created a README.md for the replicator action, mirroring the structure and content style of the commit-monitor/README.md, with adjustments to fit the replicator action's functionality and usage. This should provide clear guidance on how to use the replicator action within projects.

---

📋 Log ↩️ Undo