Use Windows runner in GitHub Actions, use python/invoke instead of ruby/rake.

.gitattributes

@@ -0,0 +1,15 @@
+# Set the default behavior, in case people don't have `core.autocrlf` set.
+* text=auto
+
+# Explicitly declare text files you want to always be normalized and converted
+# to native OS line endings on checkout, but committing those with LF in the repo.
+
+# Required for robot tests to run properly in Windows.
+**/testdata/*.txt     text  eol=lf
+**/testdata/*.yaml    text  eol=lf
+
+*.py     text
+*.js     text
+*.md     text
+*.robot  text
+*.go     text

.github/workflows/codeql-analysis.yml

@@ -0,0 +1,72 @@
+# For most projects, this workflow file will not need changing; you simply need
+# to commit it to your repository.
+#
+# You may wish to alter this file to override the set of languages analyzed,
+# or to provide custom queries or build logic.
+#
+# ******** NOTE ********
+# We have attempted to detect the languages in your repository. Please check
+# the `language` matrix defined below to confirm you have the correct set of
+# supported CodeQL languages.
+#
+name: "CodeQL"
+
+on:
+  push:
+    branches: [ "master" ]
+  pull_request:
+    # The branches below must be a subset of the branches above
+    branches: [ "master" ]
+  schedule:
+    - cron: '24 10 * * 1'
+
+jobs:
+  analyze:
+    name: Analyze
+    runs-on: ubuntu-latest
+    permissions:
+      actions: read
+      contents: read
+      security-events: write
+
+    strategy:
+      fail-fast: false
+      matrix:
+        language: [ 'go' ]
+        # CodeQL supports [ 'cpp', 'csharp', 'go', 'java', 'javascript', 'python', 'ruby' ]
+        # Learn more about CodeQL language support at https://aka.ms/codeql-docs/language-support
+
+    steps:
+    - name: Checkout repository
+      uses: actions/checkout@v4
+
+    # Initializes the CodeQL tools for scanning.
+    - name: Initialize CodeQL
+      uses: github/codeql-action/init@v3
+      with:
+        languages: ${{ matrix.language }}
+        # If you wish to specify custom queries, you can do so here or in a config file.
+        # By default, queries listed here will override any specified in a config file.
+        # Prefix the list here with "+" to use these queries and those in the config file.
+
+        # Details on CodeQL's query packs refer to : https://docs.github.com/en/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#using-queries-in-ql-packs
+        # queries: security-extended,security-and-quality
+
+
+    # Autobuild attempts to build any compiled languages  (C/C++, C#, or Java).
+    # If this step fails, then you should remove it and run the build manually (see below)
+    - name: Autobuild
+      uses: github/codeql-action/autobuild@v3
+
+    # ℹ️ Command-line programs to run using the OS shell.
+    # 📚 See https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idstepsrun
+
+    #   If the Autobuild fails above, remove it and uncomment the following three lines. 
+    #   modify them (or add more) to build your code if your project, please refer to the EXAMPLE below for guidance.
+
+    # - run: |
+    #   echo "Run, Build Application using script"
+    #   ./location_of_script_within_repo/buildscript.sh
+
+    - name: Perform CodeQL Analysis
+      uses: github/codeql-action/analyze@v3

.github/workflows/generator-generic-ossf-slsa3-publish.yml

@@ -0,0 +1,66 @@
+# This workflow uses actions that are not certified by GitHub.
+# They are provided by a third-party and are governed by
+# separate terms of service, privacy policy, and support
+# documentation.
+
+# This workflow lets you generate SLSA provenance file for your project.
+# The generation satisfies level 3 for the provenance requirements - see https://slsa.dev/spec/v0.1/requirements
+# The project is an initiative of the OpenSSF (openssf.org) and is developed at
+# https://github.com/slsa-framework/slsa-github-generator.
+# The provenance file can be verified using https://github.com/slsa-framework/slsa-verifier.
+# For more information about SLSA and how it improves the supply-chain, visit slsa.dev.
+
+name: SLSA generic generator
+on:
+  workflow_dispatch:
+  release:
+    types: [created]
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    outputs:
+      digests: ${{ steps.hash.outputs.digests }}
+
+    steps:
+      - uses: actions/checkout@v4
+
+      # ========================================================
+      #
+      # Step 1: Build your artifacts.
+      #
+      # ========================================================
+      - name: Build artifacts
+        run: |
+            # These are some amazing artifacts.
+            echo "artifact1" > artifact1
+            echo "artifact2" > artifact2
+
+      # ========================================================
+      #
+      # Step 2: Add a step to generate the provenance subjects
+      #         as shown below. Update the sha256 sum arguments
+      #         to include all binaries that you generate
+      #         provenance for.
+      #
+      # ========================================================
+      - name: Generate subject for provenance
+        id: hash
+        run: |
+          set -euo pipefail
+
+          # List the artifacts the provenance will refer to.
+          files=$(ls artifact*)
+          # Generate the subjects (base64 encoded).
+          echo "hashes=$(sha256sum $files | base64 -w0)" >> "${GITHUB_OUTPUT}"
+
+  provenance:
+    needs: [build]
+    permissions:
+      actions: read   # To read the workflow path.
+      id-token: write # To sign the provenance.
+      contents: write # To add assets to a release.
+    uses: slsa-framework/slsa-github-generator/.github/workflows/[email protected]
+    with:
+      base64-subjects: "${{ needs.build.outputs.digests }}"
+      upload-assets: true # Optional: Upload to a new release

.github/workflows/rcc.yaml

@@ -1,47 +1,76 @@
 name: Rcc
 on:
-    push:
-        branches:
-            - master
-            - maintenance
+  workflow_dispatch:
+    # enables manual triggering
+  push:
+    branches:
+      - master
+      - maintenance
+      - series10
+  pull_request:
+    branches:
+      - master
 
 jobs:
-    build:
-        name: Build
-        runs-on: ubuntu-latest
-        steps:
-            - uses: actions/checkout@v1
-            - uses: actions/setup-ruby@v1
-              with:
-                  ruby-version: '2.5'
-            - name: What
-              run: rake what
-            - name: Building
-              run: rake build
+  build:
+    name: Build
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/setup-go@v5
+        with:
+          go-version: "1.20.x"
+      - name: Set up Python 3.10
+        uses: actions/setup-python@v5
+        with:
+          python-version: "3.10"
+      - uses: actions/checkout@v4
+      - name: Install invoke
+        run: python -m pip install invoke
+      - name: What
+        run: inv what
+      - name: Building
+        run: inv build
 
-    robot:
-        name: Robot
-        runs-on: ${{ matrix.os }}-latest
-        strategy:
-            fail-fast: false
-            matrix:
-                os: ['ubuntu']
-        steps:
-            - uses: actions/checkout@v1
-            - uses: actions/setup-ruby@v1
-              with:
-                  ruby-version: '2.5'
-            - uses: actions/setup-python@v1
-              with:
-                  python-version: '3.7'
-            - name: Setup
-              run: rake robotsetup
-            - name: What
-              run: rake what
-            - name: Testing
-              run: rake robot
-            - uses: actions/upload-artifact@v1
-              if: success() || failure()
-              with:
-                  name: ${{ matrix.os }}-test-reports
-                  path: ./tmp/output/
+  robot:
+    name: Robot
+    runs-on: ${{ matrix.os }}-latest
+    strategy:
+      fail-fast: false
+      matrix:
+        os: ["ubuntu", "windows"]
+    steps:
+      - uses: actions/setup-go@v5
+        with:
+          go-version: "1.20.x"
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.10"
+      - uses: actions/checkout@v4
+      - name: Install invoke
+        run: python -m pip install invoke
+      - name: Setup
+        run: inv robotsetup
+      - name: What
+        run: inv what
+      - name: Testing
+        run: inv robot
+      - uses: actions/upload-artifact@v4
+        if: success() || failure()
+        with:
+          name: ${{ matrix.os }}-test-reports
+          path: ./tmp/output/
+
+  trigger:
+    name: Trigger
+    runs-on: ubuntu-latest
+    needs:
+      - build
+      - robot
+    if: success() && github.ref == 'refs/heads/master'
+    steps:
+      - name: Pipeline
+        run: |
+          curl -X POST https://api.github.com/repos/robocorp/rcc-pipeline/dispatches \
+          -H 'Accept: application/vnd.github.v3+json' \
+          -u ${{ secrets.TRIGGER_TOKEN }} \
+          --data '{"event_type": "pipes"}'

.gitignore

@@ -20,7 +20,10 @@ __pycache__/
 build/
 output/
 tmp/
+developer/tmp/
 rcc.yaml
 rcccache.yaml
 tags
 .DS_Store
+.use
+.idea/

.vscode/settings.json

@@ -0,0 +1,36 @@
+{
+  "python.pydev.pythonPath": [
+    ".",
+  ],
+  "python.pydev.preferredImportLocation": "topOfMethod",
+
+  "python.pydev.formatter": "ruff",
+  "python.pydev.lint.ruff.use": true,
+  "python.pydev.lint.ruff.showOutput": true,
+  "python.pydev.lint.mypy.use": true,
+  "python.pydev.lint.mypy.showOutput": true,
+  "python.pydev.lint.mypy.args": "--follow-imports=silent --show-column-numbers --namespace-packages --explicit-package-bases",
+  "python.pydev.docstring.style": "google",
+  "editor.formatOnType": true,
+  "editor.formatOnSave": true,
+  "python.pydev.sortImportsOnFormat": "isort",
+
+  "[typescript]": {
+    "editor.defaultFormatter": "esbenp.prettier-vscode"
+  },
+  "[markdown]": {
+    "editor.defaultFormatter": "esbenp.prettier-vscode"
+  },
+  "[javascript]": {
+    "editor.defaultFormatter": "esbenp.prettier-vscode"
+  },
+  "[jsonc]": {
+    "editor.defaultFormatter": "esbenp.prettier-vscode"
+  },
+  "[html]": {
+    "editor.defaultFormatter": "vscode.html-language-features"
+  },
+  "[typescriptreact]": {
+    "editor.defaultFormatter": "esbenp.prettier-vscode"
+  }
+}

CONTRIBUTING.md

@@ -0,0 +1,45 @@
+# How to contribute
+
+## Ideas for regular sources of contribution.
+
+1. Is there a need to upgrade the Go language version?
+    - see releases from https://go.dev/doc/devel/release
+    - do not go to bleeding edge (unless you really have to do so)
+    - do not stay too far away behind development
+    - when needed, update .github/workflows/rcc.yaml
+2. Is there new Micromamba available?
+    - see releases from https://anaconda.org/conda-forge/micromamba
+    - only use stable versions
+3. Where is uv going?
+    - important: uv has to come from conda-forge because of enterprise
+      firewalls/proxies
+    - https://anaconda.org/conda-forge/uv to find out what is available
+      on conda-forge
+    - https://github.com/astral-sh/uv to see issues and development
+4. What is pip doing?
+    - check news from https://pip.pypa.io/en/stable/news/
+
+## Additional sources for contribution ideas.
+
+- improve documentation under docs/ directory
+- improve acceptance tests written in Robot Framework (inside `robot_tests`
+  directory)
+    - currently these work fully on Linux only, so if you have Mac or Windows
+      and can make these work there, that would also be a nice contribution
+
+## How to proceed with improvements/contributions?
+
+- create an issue in the rcc repository at
+  https://github.com/robocorp/rcc/issues
+- on that issue, discuss the solution you are proposing
+- implementation can proceed only when the solution is clear and accepted
+- the solution should be made so that it works on Mac, Windows, and Linux
+- when developing, remember to run both unit tests and acceptance tests
+  (Robot Framework tests) on your own machine first
+- once you have written the code for that solution, create a pull request
+
+## How does rcc build work?
+
+- a good source to understand the build is to see the CI pipeline,
+  .github/workflows/rcc.yaml
+- also read docs/BUILD.md for tooling requirements and commands to run