chore(actions): implement auto check

Author: plastikfan

.github/workflows/auto-check-workflow.yml

@@ -1,4 +1,4 @@
-name: Arcadia Continuous Integration
+name: Goo Continuous Integration
 
 on:
   push:

.github/workflows/ci-workflow.yml

@@ -1,4 +1,4 @@
-name: Arcadia Release
+name: Goo Release
 
 on:
   push:

.github/workflows/release-workflow.yml

@@ -5,7 +5,7 @@ before:
     # - go mod generate
 
 builds:
-  - id: "arcadia"
+  - id: "goo"
     env:
       - CGO_ENABLED=0
     goos:

.goreleaser.yaml

@@ -1,12 +1,12 @@
-# 🦄 arcadia: ___Go template for Cobra based cli applications___
+# 🦄 goo: ___Go template for Cobra based cli applications___
 
 [![A B](https://img.shields.io/badge/branching-commonflow-informational?style=flat)](https://commonflow.org)
 [![A B](https://img.shields.io/badge/merge-rebase-informational?style=flat)](https://git-scm.com/book/en/v2/Git-Branching-Rebasing)
 [![A B](https://img.shields.io/badge/branch%20history-linear-blue?style=flat)](https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule)
-[![Go Reference](https://pkg.go.dev/badge/github.com/snivilised/arcadia.svg)](https://pkg.go.dev/github.com/snivilised/arcadia)
-[![Go report](https://goreportcard.com/badge/github.com/snivilised/arcadia)](https://goreportcard.com/report/github.com/snivilised/arcadia)
-[![Coverage Status](https://coveralls.io/repos/github/snivilised/arcadia/badge.svg?branch=master)](https://coveralls.io/github/snivilised/arcadia?branch=master&kill_cache=1)
-[![Arcadia Continuous Integration](https://github.com/snivilised/arcadia/actions/workflows/ci-workflow.yml/badge.svg)](https://github.com/snivilised/arcadia/actions/workflows/ci-workflow.yml)
+[![Go Reference](https://pkg.go.dev/badge/github.com/snivilised/goo.svg)](https://pkg.go.dev/github.com/snivilised/goo)
+[![Go report](https://goreportcard.com/badge/github.com/snivilised/goo)](https://goreportcard.com/report/github.com/snivilised/goo)
+[![Coverage Status](https://coveralls.io/repos/github/snivilised/goo/badge.svg?branch=master)](https://coveralls.io/github/snivilised/goo?branch=master&kill_cache=1)
+[![Goo Continuous Integration](https://github.com/snivilised/goo/actions/workflows/ci-workflow.yml/badge.svg)](https://github.com/snivilised/goo/actions/workflows/ci-workflow.yml)
 [![pre-commit](https://img.shields.io/badge/pre--commit-enabled-brightgreen?logo=pre-commit&logoColor=white)](https://github.com/pre-commit/pre-commit)
 [![A B](https://img.shields.io/badge/commit-conventional-commits?style=flat)](https://www.conventionalcommits.org/)
 
@@ -53,7 +53,7 @@ By using this template, there is no need to use the cobra-cli to scaffold your a
 
 ### 📝 Checklist of required changes
 
-The following is list of actions that must be performed before using this template. Most of the changes concern changing the name `Arcadia` to the name of the new application. As the template is instantiated from github, the new name will automatically replace the top level directory name, that being ___arcadia___. However, there are 2 situations at hand:
+The following is list of actions that must be performed before using this template. Most of the changes concern changing the name `Goo` to the name of the new application. As the template is instantiated from github, the new name will automatically replace the top level directory name, that being ___goo___. However, there are 2 situations at hand:
 
 1) target repo is owned by the snivilised organisation: the changes required will be made automatically after the repo has been created from the template WITHOUT user intervention
 
@@ -73,7 +73,7 @@ $ git commit -m "chore: initialise repository from template"
 $ git push
 ```
 
-➕ The following descriptions use owner name ___pandora___ and repo name ___maestro___ as an example. That is to say the client has instantiated ___arcadia___ template into github at url _github.com/pandora/maestro_
+➕ The following descriptions use owner name ___pandora___ and repo name ___maestro___ as an example. That is to say the client has instantiated ___goo___ template into github at url _github.com/pandora/maestro_
 
 #### 🤖 Automated changes
 
@@ -121,7 +121,7 @@ Of course, its up to the user what settings they use in their repo, these are ju
 
 ### 🌐 l10n Translations
 
-This template has been setup to support localisation. The default language is `en-GB` with support for `en-US`. There is a translation file for `en-US` defined as __locale/i18n/deploy/arcadia.active.en-US.json__. This is the initial translation for `en-US` that should be deployed with the app.
+This template has been setup to support localisation. The default language is `en-GB` with support for `en-US`. There is a translation file for `en-US` defined as __locale/i18n/deploy/goo.active.en-US.json__. This is the initial translation for `en-US` that should be deployed with the app.
 
 Make sure that the go-i18n package has been installed so that it can be invoked as cli, see [go-i18n](https://github.com/nicksnyder/go-i18n) for installation instructions.
 

README.md

@@ -5,7 +5,7 @@ dotenv: [".env"]
 
 vars:
   FORMAT: json
-  BINARY_NAME: arcadia
+  BINARY_NAME: goo
   DEPLOY_DIR: ./locale/i18n/deploy
   OUT_DIR: ./locale/i18n/out
   DIST_DIR: ./dist
@@ -216,7 +216,7 @@ tasks:
       - rm ./{{.OUT_DIR}}/* --recursive
 
   # extract: scans for i18m messages in source code
-  # - creates  empty out/l10n/arcadia.translate.en-US.json
+  # - creates  empty out/l10n/goo.translate.en-US.json
   # - extracts messages into out/active.en-GB.json
   #
   extract:

Taskfile.yml

@@ -1 +1 @@
-v0.3.4
+v0.1.0

VERSION

@@ -1,4 +1,4 @@
-module github.com/snivilised/arcadia
+module github.com/snivilised/goo
 
 go 1.26.0
 

go.mod

@@ -8,18 +8,18 @@ The local directory structure is as follows:
 
 - ___default___: contains the translation file created by the __newt__ (new translation task). Actually, this task creates an __active__ file (`active.en-GB.json`) in the `i18n/out` folder, the result  of which needs to be manually copied into the __active__ file in the `default` folder.
 
-- ___deploy___: contains all the translations files that are intended to be deployed with the application. There will be one per supported language and by default this template project includes a translation file for __en-US__ (`arcadia.active.en-US.json`)
+- ___deploy___: contains all the translations files that are intended to be deployed with the application. There will be one per supported language and by default this template project includes a translation file for __en-US__ (`goo.active.en-US.json`)
 
 ## ⚙️ Translation Workflow
 
 ### ✨ New Translations
 
-__goi18n__ instructs the user to manually create an empty translation message file that they want to add (eg `translate.en-US.json`). This is taken care of by the __newt__ task. Then the requirement is to run the goi18n merge \<active\> command (goi18n merge `arcadia.active.en-US.json` `arcadia.translate.en-US.json`). This has been wrapped up into the __merge__ task and the result is that the translation file `arcadia.translation.en-US.json` is populated with the messages to be translated. So the sequence goes:
+__goi18n__ instructs the user to manually create an empty translation message file that they want to add (eg `translate.en-US.json`). This is taken care of by the __newt__ task. Then the requirement is to run the goi18n merge \<active\> command (goi18n merge `goo.active.en-US.json` `goo.translate.en-US.json`). This has been wrapped up into the __merge__ task and the result is that the translation file `goo.translation.en-US.json` is populated with the messages to be translated. So the sequence goes:
 
-- run __newt__ task: (generates default language file `./locale/i18n/out/active.en-GB.json` and empty `./locale/i18n/out/us-US/arcadia.translation.en-US.json` file). This task can be run from the root folder, __goi18n__ will recursively search the directory tree for files with translate-able content, ie files with template definitions (___i18n.Message___)
-- run __merge__ task: derives a translation file for the requested language __en-US__ using 2 files as inputs: source active file (`./locale/i18n/out/active.en-GB.json`) and the empty __en-US__ translate file (`./locale/i18n/out/us-US/arcadia.translation.en-US.json`), both of which were generated in the previous step.
+- run __newt__ task: (generates default language file `./locale/i18n/out/active.en-GB.json` and empty `./locale/i18n/out/us-US/goo.translation.en-US.json` file). This task can be run from the root folder, __goi18n__ will recursively search the directory tree for files with translate-able content, ie files with template definitions (___i18n.Message___)
+- run __merge__ task: derives a translation file for the requested language __en-US__ using 2 files as inputs: source active file (`./locale/i18n/out/active.en-GB.json`) and the empty __en-US__ translate file (`./locale/i18n/out/us-US/goo.translation.en-US.json`), both of which were generated in the previous step.
 - hand the translate file to your translator for them to translate
-- rename the translate file to the active equivalent (`arcadia.translation.en-US.json`). Save this into the __deploy__ folder. This file will be deployed with the application.
+- rename the translate file to the active equivalent (`goo.translation.en-US.json`). Save this into the __deploy__ folder. This file will be deployed with the application.
 
 ### 🧩 Update Existing Translations (⚠️ not finalised)
 
@@ -36,7 +36,7 @@ However, in this template, the user can execute the following steps:
 
 - run task __update__: this will re-extract messages into `active.en-GB.json` and then runs merge to create an updated translate file.
 - hand the translate file to your translator for them to translate
-- as before, this translated file should be used to update the active file `arcadia.active.en-US.json` inside the __deploy__ folder.
+- as before, this translated file should be used to update the active file `goo.active.en-US.json` inside the __deploy__ folder.
 
 ## 🎓 Task Reference
 
@@ -64,7 +64,7 @@ Outputs:
 Inputs:
 
 - ./locale/i18n/out/active.en-GB.json
-- ./locale/i18n/out/en-US/arcadia.translate-en-US.json
+- ./locale/i18n/out/en-US/goo.translate-en-US.json
 
 Outputs: