Update from upstream repo commandpost/commandpost-app@master

.flake8rc

@@ -0,0 +1,2 @@
+[flake8]
+ignore = E501

.github/workflows/stale.yml

@@ -0,0 +1,20 @@
+name: 'Close stale Issues/PRs'
+on:
+  schedule:
+    - cron: '30 1 * * *'
+  workflow_dispatch:
+
+jobs:
+  stale:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/stale@v9
+        with:
+          stale-issue-message: 'This issue needs more information. Please see our request above.'
+          close-issue-message: 'No information was received, closing this Issue for now.'
+          stale-issue-label: 'stale'
+          days-before-issue-stale: 30
+          days-before-issue-close: 30
+          only-labels: 'needs-response'
+          days-before-pr-stale: -1
+          days-before-pr-close: -1

.gitignore

@@ -24,6 +24,7 @@ extensions/httpserver/HammerspoonCertTemplate.h
 
 ## Build generated
 build/
+artifacts/
 DerivedData/
 
 ## Various settings
@@ -42,3 +43,6 @@ xcuserdata/
 *.xccheckout
 *.xcscmblueprint
 
+.vscode
+
+Brewfile.lock.json

.luacheckrc

@@ -1,2 +1,57 @@
-globals = {"hs", "rawrequire"}
-ignore = {"631"}
+--
+-- These globals can be set and accessed:
+--
+globals = {
+    "rawrequire",
+}
+
+--
+-- These globals can only be accessed:
+--
+read_globals = {
+    "hs",
+    "ls",
+    "spoon",
+}
+
+--
+-- Hammerspoon Tests:
+--
+files["**/test_*.lua"] = {
+    read_globals = {
+        "assertFalse",
+        "assertGreaterThan",
+        "assertGreaterThanOrEqualTo",
+        "assertIsAlmostEqual",
+        "assertIsBoolean",
+        "assertIsEqual",
+        "assertIsFunction",
+        "assertIsNil",
+        "assertIsNotNil",
+        "assertIsNumber",
+        "assertIsString",
+        "assertIsTable",
+        "assertIsType",
+        "assertIsUserdata",
+        "assertIsUserdataOfType",
+        "assertLessThan",
+        "assertLessThanOrEqualTo",
+        "assertListsEqual",
+        "assertTableNotEmpty",
+        "assertTablesEqual",
+        "assertTrue",
+        "failure",
+        "success",
+    },
+    ignore = {
+        "111", -- Setting an undefined global variable
+        "501" -- Line too long
+    }
+}
+
+--
+-- Warnings to ignore:
+--
+ignore = {
+    "631" -- Line is too long.
+}

.stickler.yml

@@ -1,5 +1,6 @@
 linters:
     flake8:
+        config: '.flake8rc'
     shellcheck:
         shell: bash
     luacheck:

Brewfile

@@ -0,0 +1,10 @@
+tap "a7ex/homebrew-formulae"
+
+brew "coreutils"
+brew "jq"
+brew "xcbeautify"
+brew "gawk"
+brew "cocoapods"
+brew "gh"
+brew "gpg"
+brew "a7ex/homebrew-formulae/xcresultparser"

CONTRIBUTING.md

@@ -1,26 +1,27 @@
 # Contributing to Hammerspoon
 
-* [How is everything built?](#how-is-everything-built)
-    * [Making frequent local rebuilds more convenient](#making-frequent-local-rebuilds-more-convenient)
-* [Contributing to the core app or LuaSkin](#contributing-to-the-core-app-or-luaskin)
-* [Contributing to the extensions](#contributing-to-the-extensions)
-    * [Writing a new, pure-Lua extension](#writing-a-new-pure-lua-extension)
-    * [Writing a new mixed Lua/Objective-C extension](#writing-a-new-mixed-luaobjective-c-extension)
-    * [Documenting your extension](#documenting-your-extension)
-        * [Constants](#constants)
-        * [Variables](#variables)
-        * [Functions](#functions)
-        * [Methods](#methods)
-    * [Testing](#testing)
-    * [Third party extension distribution](#third-party-extension-distribution)
+- [Contributing to Hammerspoon](#contributing-to-hammerspoon)
+  - [How is everything built?](#how-is-everything-built)
+    - [Making frequent local rebuilds more convenient](#making-frequent-local-rebuilds-more-convenient)
+  - [Contributing to the core app or LuaSkin](#contributing-to-the-core-app-or-luaskin)
+  - [Contributing to the extensions](#contributing-to-the-extensions)
+    - [Writing a new, pure-Lua extension](#writing-a-new-pure-lua-extension)
+    - [Writing a new mixed Lua/Objective-C extension](#writing-a-new-mixed-luaobjective-c-extension)
+    - [Documenting your extension](#documenting-your-extension)
+      - [Constants](#constants)
+      - [Variables](#variables)
+      - [Functions](#functions)
+      - [Methods](#methods)
+    - [Testing](#testing)
+    - [Third party extension distribution](#third-party-extension-distribution)
 
 Hammerspoon is composed of three separate logical areas - a Lua runtime wrapper framework called [LuaSkin](http://www.hammerspoon.org/docs/LuaSkin/Classes/LuaSkin/index.html#), the core Hammerspoon app which houses the LuaSkin/Lua runtime and provides the ability to load extensions, and [various extension modules](https://github.com/Hammerspoon/hammerspoon/tree/master/extensions) that [expose system APIs](http://www.hammerspoon.org/docs/) to the user's Lua code.
 
 ## How is everything built?
 
-The app itself is built using Xcode. You must open `Hammerspoon.xcworkspace` rather than `Hammerspoon.xcodeproj`. If you open the latter, your build will fail because Xcode will not know about the Cocoapods that Hammerspoon depends on (see our [`Podfile`](https://github.com/Hammerspoon/hammerspoon/blob/master/Podfile) for the current list of required pods).
+The app itself is built using Xcode. You must open `Hammerspoon.xcworkspace` rather than `Hammerspoon.xcodeproj`. If you open the latter, your build will fail because Xcode will not know about the Cocoapods that Hammerspoon depends on (see our [`Podfile`](https://github.com/Hammerspoon/hammerspoon/blob/master/Podfile) for the current list of required pods). On versions of macOS prior to Catalina [Python 3](https://www.python.org) will need to be installed for the build to work.
 
-The extension modules are built before the core Hammerspoon binary as target dependencies. Each extension is defined as an Xcode target in its own right, although there is usually no reason to build these targets manually. During the late stages of the build process, a script ([`scripts/copy_extensions_to_bundle.sh`](https://github.com/Hammerspoon/hammerspoon/blob/master/scripts/copy_extensions_to_bundle.sh)) collects all of the compiled extension libraries and their associated Lua components, and inserts them into the final `Hammerspoon.app` bundle.
+The extension modules are built before the core Hammerspoon binary as target dependencies. Each extension is defined as an Xcode target in its own right, although there is usually no reason to build these targets manually.
 
 ### Making frequent local rebuilds more convenient
 [Self-signing your builds](https://github.com/Hammerspoon/hammerspoon/issues/643#issuecomment-158291705) will keep you from having to re-enable permissions for your locally built copy.
@@ -37,7 +38,7 @@ This is generally very simple in terms of the workflow, but there's less likely
 * Make the changes you want
 * Push them up to a fork on GitHub
 * Propose a Pull Request on GitHub
-* Talk to us in #hammerspoon on Freenode if you need any guidance
+* Talk to us in #hammerspoon on Libera if you need any guidance
 
 ## Contributing to the extensions
 
@@ -56,13 +57,13 @@ To create such an extension:
 * Clone the Hammerspoon git repository
 * cd into the `extensions` directory
 * Make a directory for your extension
-* Create an `init.lua` to contain your code. It should behave like any normal Lua library - that is to say, your job is to return a table containing functions/methods/constants/etc
+* Create a `modulename.lua` to contain your code, giving it the appropriate name. It should behave like any normal Lua library - that is to say, your job is to return a table containing functions/methods/constants/etc
 * Ensure you document your API in our preferred format (see the code for almost any existing module for reference)
-* Edit `scripts/copy_extensions_to_bundle.sh` and add your module name to the `HS_LUAONLY` section
+* In Xcode's Project Navigator, select the Hammerspoon root entry, then choose Hammerspoon from the Targets list and find the "Copy Extension Lua Files" build phase. Add your new Lua file
 * Build Hammerspoon and test your extension
 * Push your changes up to a fork on GitHub
 * Propose a Pull Request on GitHub
-* Talk to us in #hammerspoon on Freenode if you need any guidance
+* Talk to us in #hammerspoon on Libera if you need any guidance
 
 ### Writing a new mixed Lua/Objective-C extension ###
 
@@ -74,27 +75,27 @@ To create such an extension:
 * Create the directories/files for your extension:
   * cd into the `extensions` directory
   * Make a directory for your extension
-  * Create an `init.lua` to load your Objective-C code and contain any additional Lua code. You might find it easier to provide much of your API in Lua and just provide undocumented API from Objective C that does the minimum work possible. The choice is ultimately down to you, depending on the nature of the work the extension is doing.
-  * Create an `internal.m` to contain your Objective-C code. Please use the LuaSkin methods to do as much work as possible, they are well tested and in most extensions can reduce the amount of Lua C API calls to almost zero. Not all of our extensions have been fully converted to LuaSkin yet (a good example is [`hs.chooser`](https://github.com/Hammerspoon/hammerspoon/blob/master/extensions/chooser/internal.m))
-  * Right click on the `extensions` group in Xcode's Project Browser and add a new sub-group for your extension, then right click on the sub-group and add your `init.lua` and `internal.m` files (and any supporting `.h`/`.c`/`.m`/etc files)
-  * The files you've added will probably be made members of the Hammerspoon target. You do not want this; Select each file in the Project Browser and using the File Inspector in the Utilities pane on the right of Xcode's window, deselect them from the maim Hammerspoon target.
+  * Create a `modulename.lua` to load your Objective-C code and contain any additional Lua code. You might find it easier to provide much of your API in Lua and just provide undocumented API from Objective C that does the minimum work possible. The choice is ultimately down to you, depending on the nature of the work the extension is doing.
+  * Create a `modulename.m` to contain your Objective-C code. Please use the LuaSkin methods to do as much work as possible, they are well tested and in most extensions can reduce the amount of Lua C API calls to almost zero. Not all of our extensions have been fully converted to LuaSkin yet (a good example is [`hs.chooser`](https://github.com/Hammerspoon/hammerspoon/blob/master/extensions/chooser/internal.m))
+  * Right click on the `extensions` group in Xcode's Project Browser and add a new sub-group for your extension, then right click on the sub-group and add your `modulename.lua` and `modulename.m` files (and any supporting `.h`/`.c`/`.m`/etc files)
+  * The files you've added will probably be made members of the Hammerspoon target. You do not want this; Select each file in the Project Browser and using the File Inspector in the Utilities pane on the right of Xcode's window, deselect them from the main Hammerspoon target.
 * Configure Xcode to build your extension and include it in the `Hammerspoon.app` bundle:
   * Click on the `Hammerspoon` workspace at the very top of the Xcode Project Browser (i.e. the bar on the left)
-  * Right click on `alert` in the "project and targets list" and choose `Duplicate`, which creates `alert copy` at the bottom of the list.
+  * Right click on an existing extension target in the "project and targets list" and choose `Duplicate`, which creates `extensionname copy` at the bottom of the list.
   * Rename the copy and drag it to the right place in the list (alphabetically)
-  * Click on the target you just created, remove hs.alert's `internal.m` from the `Compile Sources` build phase, add in the `.m` files from your new module
-  * Check the `Link Binary With Libraries` section for any frameworks you need to add. Typically this will jsut mean `LuaSkin.framework`, plus any additional system frameworks you need to link against.
+  * Click on the target you just created, remove hs.alert's `extension.m` from the `Compile Sources` build phase, add in the `.m` files from your new module
+  * Check the `Link Binary With Libraries` section for any frameworks you need to add. Typically this will just mean `LuaSkin.framework`, plus any additional system frameworks you need to link against.
   * Click on the `Hammerspoon` target (not the project), and in the `Target Dependencies` build phase, add the module target you just created
-  * Click the menu item Product → Scheme → Manage Schemes, find `alert copy`, rename it and move it to the right place in the list of schemes
-  * Edit `scripts/copy_extensions_to_bundle.sh` and add your module name to the `HS_MODULES` section. *Note*: Some modules may also need to copy extra files into the app bundle, in which case add a "special copier" to the bottom of the script.
+  * Click the menu item Product → Scheme → Manage Schemes, find `extensionname copy`, rename it and move it to the right place in the list of schemes
+  * Add your `modulename.lua` to the "Copy Extension Lua Files" build phase on the Hammerspoon target, and your `modulename.dylib` to the "Copy Extension Dylibs" build phase
 * Build Hammerspoon and test your extension
 * Push your changes up to a fork on GitHub
 * Propose a Pull Request on GitHub
-* Talk to us in #hammerspoon on Freenode if you need any guidance
+* Talk to us in #hammerspoon on Libera if you need any guidance
 
 ### Documenting your extension
 
-Both Lua and Objective-C portions of an extension should contain in-line documention of all of the functions they expose to users of the extension.
+Both Lua and Objective-C portions of an extension should contain in-line documentation of all of the functions they expose to users of the extension.
 
 The format for docstrings should follow the standard described below. Note that for Lua files, the lines should begin with `---` and for Objective C files, the lines should begin with `///`.
 
@@ -169,7 +170,7 @@ The best place to start is in the `Hammerspoon/Hammerspoon Tests` folder in Xcod
  * The rest of `HSfoo` should be methods named `testBar`, each of which causes some test action to take place.
  * There are some helper macros for use inside the test methods:
   * `RUN_LUA_TEST()` will cause a function from `test_foo.lua` to be run, if its name exactly matches the name of the `HSfoo` method
-  * `SKIP_IN_TRAVIS()` will cause this test to be skipped when running as part of our [Travis](http://www.travis-ci.org) test runs (e.g. because the Travis VMs lack hardware/network resources required to test)
+  * `SKIP_IN_GITHUB_ACTIONS()` will cause this test to be skipped when running as part of our GitHub Actions test runs (e.g. because the GitHub VMs lack hardware/network resources required to test)
 
 When Hammerspoon detects it is is being run by `XCTest`, it loads a special `init.lua` (`Hammerspoon/Hammerspoon Tests/init.lua`) which provides a number of helper functions, mainly related to asserting state in test functions. These functions will generate Lua errors if a test failure occurs, which will cause Xcode to report the test has failed, with an appropriate backtrace in the logs. Refer to the file for the full list of assertions, but the most useful are:
 

CREDITS.md

@@ -1,21 +1,10 @@
-Hammerspoon is based on Mjolnir by Steven Degutis, which is based on Hydra by Steven Degutis.
+Hammerspoon is based on Mjolnir, which is based on Hydra.
 
-The extensions included in Hammerspoon were written by:
- * [Steven Degutis](https://github.com/sdegutis/)
- * [Aaron Magill](https://github.com/asmagill)
+Our maintainers are:
  * [Chris Jones](https://github.com/cmsj)
- * Peter van Dijk
- * Linell Bonnette
- * Kepler Project
- * Enrique García Cota
- * Szymon Kaliski
- * Brian Gilbert
- * Tristan Hume
- * Tyler Mandry
- * Alexander Yakushev
- * Jake Heinz
- * Till Klocke
- * Markus Engelbrecht
+ * [Aaron Magill](https://github.com/asmagill)
  * [Chris Hocking](https://github.com/latenitefilms)
 
-The Hammerspon icon was provided by Juerd Waalboer.
+Lots of additional extensions/work has been provided by [various contributors](https://github.com/Hammerspoon/hammerspoon/graphs/contributors)
+
+The Hammerspoon icon was provided by Juerd Waalboer.

CommandPost Workflow Extension/Assets/Assets.xcassets/AppIcon.appiconset/Contents.json

@@ -0,0 +1,68 @@
+{
+  "images" : [
+    {
+      "filename" : "icon_16x16.png",
+      "idiom" : "mac",
+      "scale" : "1x",
+      "size" : "16x16"
+    },
+    {
+      "filename" : "icon_16x16@2x@2x.png",
+      "idiom" : "mac",
+      "scale" : "2x",
+      "size" : "16x16"
+    },
+    {
+      "filename" : "icon_32x32.png",
+      "idiom" : "mac",
+      "scale" : "1x",
+      "size" : "32x32"
+    },
+    {
+      "filename" : "icon_32x32@2x@2x.png",
+      "idiom" : "mac",
+      "scale" : "2x",
+      "size" : "32x32"
+    },
+    {
+      "filename" : "icon_128x128.png",
+      "idiom" : "mac",
+      "scale" : "1x",
+      "size" : "128x128"
+    },
+    {
+      "filename" : "icon_128x128@2x@2x.png",
+      "idiom" : "mac",
+      "scale" : "2x",
+      "size" : "128x128"
+    },
+    {
+      "filename" : "icon_256x256.png",
+      "idiom" : "mac",
+      "scale" : "1x",
+      "size" : "256x256"
+    },
+    {
+      "filename" : "icon_256x256@2x@2x.png",
+      "idiom" : "mac",
+      "scale" : "2x",
+      "size" : "256x256"
+    },
+    {
+      "filename" : "icon_512x512.png",
+      "idiom" : "mac",
+      "scale" : "1x",
+      "size" : "512x512"
+    },
+    {
+      "filename" : "icon_512x512@2x@2x.png",
+      "idiom" : "mac",
+      "scale" : "2x",
+      "size" : "512x512"
+    }
+  ],
+  "info" : {
+    "author" : "xcode",
+    "version" : 1
+  }
+}

CommandPost Workflow Extension/CommandPost-Bridging-Header.h

@@ -0,0 +1 @@
+#import <ProExtension/ProExtension.h>