Cli

.changeset/clippy-stable-lints.md

@@ -0,0 +1,5 @@
+---
+"@googleworkspace/cli": patch
+---
+
+Fix stable Clippy warnings in the token provider and Apps Script file matching

.cursor/environment.json

@@ -0,0 +1,4 @@
+{
+  "name": "gws",
+  "install": "rustup toolchain install stable --profile minimal --component rustfmt,clippy\nrustup default stable\ncargo fetch --locked\npnpm install --frozen-lockfile --ignore-scripts"
+}

.github/FUNDING.yml

@@ -0,0 +1,98 @@
+# These are supported funding model platforms
+
+github: # Replace with up to 4 GitHub Sponsors-enabled usernames e.g., [user1, user2]
+patreon: # Replace with a single Patreon username
+open_collective: # Replace with a single Open Collective username
+ko_fi: # Replace with a single Ko-fi username
+tidelift: # Replace with a single Tidelift platform-name/package-name e.g., npm/babel
+community_bridge: # Replace with a single Community Bridge project-name e.g., cloud-foundry
+liberapay: # Replace with a single Liberapay username
+issuehunt: # Replace with a single IssueHunt username
+lfx_crowdfunding: # Replace with a single LFX Crowdfunding project-name e.g., cloud-foundry
+polar: # Replace with a single Polar username
+buy_me_a_coffee: # Replace with a single Buy Me a Coffee username
+thanks_dev: # Replace with a single thanks.dev username
+custom: # Replace with up to 4 custom sponsorship URLs e.g., ['link1', 'link2']
+# Displaying a sponsor button in your repository
+
+You can add a sponsor button in your repository to increase the visibility of funding options for your open source project.
+
+## About FUNDING files
+
+You can configure your sponsor button by editing a `FUNDING.yml` file in your repository's `.github` folder, on the default branch. You can configure the button to include sponsored developers in GitHub Sponsors, external funding platforms, or a custom funding URL. For more information about GitHub Sponsors, see [About GitHub Sponsors](/en/sponsors/getting-started-with-github-sponsors/about-github-sponsors).
+
+You can add one username, package name, or project name per external funding platform and up to four custom URLs. You can add one organization and up to four sponsored developers in GitHub Sponsors. Add each platform on a new line, using the following syntax.
+
+| Platform                                                                                      | Syntax                                                                   |
+| --------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------ |
+| [LFX Mentorship (formerly CommunityBridge)](https://lfx.linuxfoundation.org/tools/mentorship) | `community_bridge: PROJECT-NAME`                                         |
+| [GitHub Sponsors](https://github.com/sponsors)                                                | `github: USERNAME` or `github: [USERNAME, USERNAME, USERNAME, USERNAME]` |
+| [IssueHunt](https://issuehunt.io/)                                                            | `issuehunt: USERNAME`                                                    |
+| [Ko-fi](https://ko-fi.com/)                                                                   | `ko_fi: USERNAME`                                                        |
+| [Liberapay](https://en.liberapay.com/)                                                        | `liberapay: USERNAME`                                                    |
+| [Open Collective](https://opencollective.com/)                                                | `open_collective: USERNAME`                                              |
+| [Patreon](https://www.patreon.com/)                                                           | `patreon: USERNAME`                                                      |
+| [Tidelift](https://tidelift.com/)                                                             | `tidelift: PLATFORM-NAME/PACKAGE-NAME`                                   |
+| [Polar](https://www.polar.sh/)                                                                | `polar: USERNAME`                                                        |
+| [Buy Me a Coffee](https://www.buymeacoffee.com/)                                              | `buy_me_a_coffee: USERNAME`                                              |
+| [thanks.dev](https://thanks.dev/)                                                             | `thanks_dev: u/gh/USERNAME`                                              |
+| Custom URL                                                                                    | `custom: LINK1` or `custom: [LINK1, LINK2, LINK3, LINK4]`                |
+
+For Tidelift, use the `platform-name/package-name` syntax with the following platform names.
+
+| Language   | Platform name |
+| ---------- | ------------- |
+| JavaScript | `npm`         |
+| Python     | `pypi`        |
+| Ruby       | `rubygems`    |
+| Java       | `maven`       |
+| PHP        | `packagist`   |
+| C#         | `nuget`       |
+
+Here's an example `FUNDING.yml` file:
+
+```yaml
+github: [octocat, surftocat]
+patreon: octocat
+tidelift: npm/octo-package
+custom: ["https://www.paypal.me/octocat", octocat.com]
+```
+
+> \[!NOTE]
+> If a custom URL in an array includes `:`, you must wrap the URL in quotes. For example, `"https://www.paypal.me/octocat"`.
+
+You can create a default sponsor button for your organization or personal account. For more information, see [Creating a default community health file](/en/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file).
+
+> \[!NOTE]
+> Funding links provide a way for open source projects to receive direct financial support from their community. We don’t support the use of funding links for other purposes, such as for advertising, or supporting political, community, or charity groups. If you have questions about whether your intended use is supported, please visit [GitHub Support](https://support.github.com).
+
+## Displaying a sponsor button in your repository
+
+Anyone with admin permissions can enable a sponsor button in a repository.
+
+1. On GitHub, navigate to the main page of the repository.
+
+2. Under your repository name, click **<svg version="1.1" width="16" height="16" viewBox="0 0 16 16" class="octicon octicon-gear" aria-label="gear" role="img"><path d="M8 0a8.2 8.2 0 0 1 .701.031C9.444.095 9.99.645 10.16 1.29l.288 1.107c.018.066.079.158.212.224.231.114.454.243.668.386.123.082.233.09.299.071l1.103-.303c.644-.176 1.392.021 1.82.63.27.385.506.792.704 1.218.315.675.111 1.422-.364 1.891l-.814.806c-.049.048-.098.147-.088.294.016.257.016.515 0 .772-.01.147.038.246.088.294l.814.806c.475.469.679 1.216.364 1.891a7.977 7.977 0 0 1-.704 1.217c-.428.61-1.176.807-1.82.63l-1.102-.302c-.067-.019-.177-.011-.3.071a5.909 5.909 0 0 1-.668.386c-.133.066-.194.158-.211.224l-.29 1.106c-.168.646-.715 1.196-1.458 1.26a8.006 8.006 0 0 1-1.402 0c-.743-.064-1.289-.614-1.458-1.26l-.289-1.106c-.018-.066-.079-.158-.212-.224a5.738 5.738 0 0 1-.668-.386c-.123-.082-.233-.09-.299-.071l-1.103.303c-.644.176-1.392-.021-1.82-.63a8.12 8.12 0 0 1-.704-1.218c-.315-.675-.111-1.422.363-1.891l.815-.806c.05-.048.098-.147.088-.294a6.214 6.214 0 0 1 0-.772c.01-.147-.038-.246-.088-.294l-.815-.806C.635 6.045.431 5.298.746 4.623a7.92 7.92 0 0 1 .704-1.217c.428-.61 1.176-.807 1.82-.63l1.102.302c.067.019.177.011.3-.071.214-.143.437-.272.668-.386.133-.066.194-.158.211-.224l.29-1.106C6.009.645 6.556.095 7.299.03 7.53.01 7.764 0 8 0Zm-.571 1.525c-.036.003-.108.036-.137.146l-.289 1.105c-.147.561-.549.967-.998 1.189-.173.086-.34.183-.5.29-.417.278-.97.423-1.529.27l-1.103-.303c-.109-.03-.175.016-.195.045-.22.312-.412.644-.573.99-.014.031-.021.11.059.19l.815.806c.411.406.562.957.53 1.456a4.709 4.709 0 0 0 0 .582c.032.499-.119 1.05-.53 1.456l-.815.806c-.081.08-.073.159-.059.19.162.346.353.677.573.989.02.03.085.076.195.046l1.102-.303c.56-.153 1.113-.008 1.53.27.161.107.328.204.501.29.447.222.85.629.997 1.189l.289 1.105c.029.109.101.143.137.146a6.6 6.6 0 0 0 1.142 0c.036-.003.108-.036.137-.146l.289-1.105c.147-.561.549-.967.998-1.189.173-.086.34-.183.5-.29.417-.278.97-.423 1.529-.27l1.103.303c.109.029.175-.016.195-.045.22-.313.411-.644.573-.99.014-.031.021-.11-.059-.19l-.815-.806c-.411-.406-.562-.957-.53-1.456a4.709 4.709 0 0 0 0-.582c-.032-.499.119-1.05.53-1.456l.815-.806c.081-.08.073-.159.059-.19a6.464 6.464 0 0 0-.573-.989c-.02-.03-.085-.076-.195-.046l-1.102.303c-.56.153-1.113.008-1.53-.27a4.44 4.44 0 0 0-.501-.29c-.447-.222-.85-.629-.997-1.189l-.289-1.105c-.029-.11-.101-.143-.137-.146a6.6 6.6 0 0 0-1.142 0ZM11 8a3 3 0 1 1-6 0 3 3 0 0 1 6 0ZM9.5 8a1.5 1.5 0 1 0-3.001.001A1.5 1.5 0 0 0 9.5 8Z"></path></svg> Settings**. If you cannot see the "Settings" tab, select the **<svg version="1.1" width="16" height="16" viewBox="0 0 16 16" class="octicon octicon-kebab-horizontal" aria-label="More" role="img"><path d="M8 9a1.5 1.5 0 1 0 0-3 1.5 1.5 0 0 0 0 3ZM1.5 9a1.5 1.5 0 1 0 0-3 1.5 1.5 0 0 0 0 3Zm13 0a1.5 1.5 0 1 0 0-3 1.5 1.5 0 0 0 0 3Z"></path></svg>** dropdown menu, then click **Settings**.
+
+   ![Screenshot of a repository header showing the tabs. The "Settings" tab is highlighted by a dark orange outline.](/assets/images/help/repository/repo-actions-settings.png)
+
+3. On the "General" settings page, in the "Features" section, select **Sponsorships**.
+
+4. In the "Sponsorships" box, click **Set up sponsor button** or **Override funding links**.
+
+5. In the file editor, follow the instructions in the `FUNDING.yml` file to add links to your funding locations.
+
+6. Click **Commit changes...**
+
+7. In the "Commit message" field, type a short, meaningful commit message that describes the change you made to the file. You can attribute the commit to more than one author in the commit message. For more information, see [Creating a commit with multiple authors or on behalf of an organization](/en/pull-requests/how-tos/commit-changes/creating-a-commit-with-multiple-authors).
+
+8. Below the commit message fields, decide whether to add your commit to the current branch or to a new branch. If your current branch is the default branch, you should choose to create a new branch for your commit and then create a pull request. For more information, see [Creating a pull request](/en/pull-requests/how-tos/create-pull-requests/creating-a-pull-request).
+
+   ![Screenshot of a GitHub pull request showing a radio button to commit directly to the main branch or to create a new branch. New branch is selected.](/assets/images/help/repository/choose-commit-branch.png)
+
+9. Click **Commit changes** or **Propose changes**.
+
+## Further reading
+
+* [About GitHub Sponsors for open source contributors](/en/sponsors/receiving-sponsorships-through-github-sponsors/about-github-sponsors-for-open-source-contributors)
+* [FAQ with the GitHub Sponsors team](https://github.blog/2019-06-12-faq-with-the-github-sponsors-team/) on the GitHub Blog

AGENTS.md

@@ -237,3 +237,20 @@ See [`src/helpers/README.md`](crates/google-workspace-cli/src/helpers/README.md)
 | `GOOGLE_WORKSPACE_CLI_LOG_FILE` | Directory for JSON-line log files with daily rotation. Off by default. |
 
 All variables can also live in a `.env` file (loaded via `dotenvy`).
+
+## Cursor Cloud specific instructions
+
+Cloud Agent install is defined in `.cursor/environment.json`. The default Cloud Agent image ships Rust 1.83. This repository's lockfile includes Edition 2024 crates, which need stable Rust (1.85 or newer). Before `cargo fetch`, `cargo test`, or `cargo clippy`, install and select stable:
+
+```bash
+rustup toolchain install stable --profile minimal --component rustfmt,clippy
+rustup default stable
+```
+
+`pnpm install` runs `lefthook install` through the `prepare` script. That command fails while Cursor sets `core.hooksPath`. Install Node dependencies with:
+
+```bash
+pnpm install --frozen-lockfile --ignore-scripts
+```
+
+`gws schema <service.resource.method>` and `gws <service> <resource> <method> --help` fetch Discovery documents from `www.googleapis.com` and do not need Google credentials. Calling a live API method needs OAuth (`gws auth login`) or `GOOGLE_WORKSPACE_CLI_TOKEN`.

crates/google-workspace-cli/src/auth.rs

@@ -137,6 +137,9 @@ enum Credential {
 ///
 /// Long-running helpers use this trait so they can request a fresh token before
 /// each API call instead of holding a single token string until it expires.
+// async-trait adds `#[must_use]` with no reason on the boxed future. That
+// future is already must-use, so stable Clippy rejects the attribute.
+#[allow(clippy::double_must_use)]
 #[async_trait::async_trait]
 pub trait AccessTokenProvider: Send + Sync {
     async fn access_token(&self) -> anyhow::Result<String>;

crates/google-workspace-cli/src/helpers/script.rs

@@ -169,13 +169,7 @@ fn process_file(path: &Path) -> Result<Option<serde_json::Value>, GwsError> {
             filename.trim_end_matches(".js").trim_end_matches(".gs"),
         ),
         "html" => ("HTML", filename.trim_end_matches(".html")),
-        "json" => {
-            if filename == "appsscript.json" {
-                ("JSON", "appsscript")
-            } else {
-                return Ok(None);
-            }
-        }
+        "json" if filename == "appsscript.json" => ("JSON", "appsscript"),
         _ => return Ok(None),
     };