From a51660f796c57196db74d642a1f790afa6a677f0 Mon Sep 17 00:00:00 2001 From: Ksenia Kotelnikova Date: Tue, 28 Oct 2025 14:03:10 +0300 Subject: [PATCH 01/10] feat: README Signed-off-by: Ksenia Kotelnikova --- README.md | 20 ++++++++++++++++++++ 1 file changed, 20 insertions(+) diff --git a/README.md b/README.md index 708471c..44a7369 100644 --- a/README.md +++ b/README.md @@ -1,2 +1,22 @@ # rusty_ache Blazingly fast game engine written in Rust. + +## How to run +Clone this repo: +```bash + git clone git@github.com:WoWaster/Geraltt.git +``` +Open project: +```bash + cd spbu-tt-diff-notify +``` +Run project: +```bash + cargo run --bin main +``` + +## Devs +* [Aleksei Dmitrievstev](https://github.com/admitrievtsev) +* [Ksenia Kotelnikova](https://github.com/p1onerka) +* [Sofya Kozyreva](https://github.com/sofyak0zyreva) +* [Kostya Oreshin](https://github.com/sevenbunu) \ No newline at end of file From 1e640c48f043043cbabe5a004dacdbb5265c45c6 Mon Sep 17 00:00:00 2001 From: Ksenia Kotelnikova Date: Wed, 29 Oct 2025 22:05:01 +0300 Subject: [PATCH 02/10] feat: CONTRIBUTING.md Signed-off-by: Ksenia Kotelnikova --- CONTRIBUTING.md | 88 +++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 88 insertions(+) create mode 100644 CONTRIBUTING.md diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md new file mode 100644 index 0000000..fb2ad44 --- /dev/null +++ b/CONTRIBUTING.md @@ -0,0 +1,88 @@ +# Contributing to rusty_ache + +All types of contributions are encouraged and valued. See the [Table of Contents](#table-of-contents) for different ways to help and details about how this project handles them. Please make sure to read the relevant section before making your contribution. It will make it a lot easier for us maintainers and smooth out the experience for all involved. The community looks forward to your contributions. + +## Table of Contents + +- [I Have a Question](#i-have-a-question) +- [I Want To Contribute](#i-want-to-contribute) +- [Reporting Bugs](#reporting-bugs) +- [Suggesting Enhancements](#suggesting-enhancements) + + +## I Have a Question + +> If you want to ask a question, we assume that you have read the available [Documentation](https://github.com/p1onerka/rusty_ache/blob/main/README.md). + +Before you ask a question, it is best to search for existing [Issues](https://github.com/p1onerka/rusty_ache/tree/main/issues) that might help you. In case you have found a suitable issue and still need clarification, you can write your question in this issue. + +If you then still feel the need to ask a question and need clarification, we recommend the following: + +- Open an [Issue](https://github.com/p1onerka/rusty_ache/tree/main/issues/new). +- Provide as much context as you can about what you're running into. +- Provide project and platform versions, depending on what seems relevant. + +We will then take care of the issue as soon as possible. + +## I Want To Contribute + +> ### Legal Notice +> When contributing to this project, you must agree that you have authored 100% of the content, that you have the necessary rights to the content and that the content you contribute may be provided under the project licence. + +### Reporting Bugs + +#### Before Submitting a Bug Report + +A good bug report shouldn't leave others needing to chase you up for more information. Therefore, we ask you to investigate carefully, collect information and describe the issue in detail in your report. Please complete the following steps in advance to help us fix any potential bug as fast as possible. + +- Make sure that you are using the latest version. +- Determine if your bug is really a bug and not an error on your side e.g. using incompatible environment components/versions (Make sure that you have read the [documentation](https://github.com/p1onerka/rusty_ache/blob/main/README.md). If you are looking for support, you might want to check [this section](#i-have-a-question)). +- To see if other users have experienced (and potentially already solved) the same issue you are having, check if there is not already a bug report existing for your bug or error in the [bug tracker](https://github.com/p1onerka/rusty_ache/tree/main/issues?q=label%3Abug). +- Collect information about the bug: +- Stack trace (Traceback) +- OS, Platform and Version (Windows, Linux, macOS, x86, ARM) +- Version of the compiler, SDK, runtime environment, depending on what seems relevant. +- Possibly your input and the output +- Can you reliably reproduce the issue? And can you also reproduce it with older versions? + +#### How Do I Submit a Good Bug Report? + +> You must never report security related issues, vulnerabilities or bugs including sensitive information to the issue tracker, or elsewhere in public. Instead sensitive bugs must be sent by email to xeniia.ka@gmail.com. + +We use GitHub issues to track bugs and errors. If you run into an issue with the project: + +- Open an [Issue](https://github.com/p1onerka/rusty_ache/tree/main/issues/new). +- Explain the behavior you would expect and the actual behavior. +- Please provide as much context as possible and describe the *reproduction steps* that someone else can follow to recreate the issue on their own. For good bug reports you should isolate the problem and create a reduced test case. +- Provide the information you collected in the previous section. + +Once it's filed: + +- The project team will label the issue accordingly. +- A team member will try to reproduce the issue with your provided steps. If there are no reproduction steps or no obvious way to reproduce the issue, the team will ask you for those steps. +- If the team is able to reproduce the issue, it will be marked `needs-fix`, as well as possibly other tags (such as `critical`), and the issue will be left to be [implemented by someone](#your-first-code-contribution). + + +### Suggesting Enhancements + +This section guides you through submitting an enhancement suggestion for rusty_ache including completely new features and minor improvements to existing functionality. Following these guidelines will help maintainers and the community to understand your suggestion and find related suggestions. + +#### Before Submitting an Enhancement + +- Make sure that you are using the latest version. +- Read the [documentation](https://github.com/p1onerka/rusty_ache/blob/main/README.md) carefully and find out if the functionality is already covered, maybe by an individual configuration. +- Perform a [search](https://github.com/p1onerka/rusty_ache/tree/main/issues) to see if the enhancement has already been suggested. If it has, add a comment to the existing issue instead of opening a new one. +- Find out whether your idea fits with the scope and aims of the project. It's up to you to make a strong case to convince the project's developers of the merits of this feature. Keep in mind that we want features that will be useful to the majority of our users and not just a small subset. If you're just targeting a minority of users, consider writing an add-on/plugin library. + +#### How Do I Submit a Good Enhancement Suggestion? + +Enhancement suggestions are tracked as [GitHub issues](https://github.com/p1onerka/rusty_ache/tree/main/issues). + +- Use a clear and descriptive title for the issue to identify the suggestion. +- Provide a step-by-step description of the suggested enhancement in as many details as possible. +- Describe the current behavior and explain which behavior you expected to see instead and why. At this point you can also tell which alternatives do not work for you. +- You may want to include screenshots or screen recordings which help you demonstrate the steps or point out the part which the suggestion is related to. +- Explain why this enhancement would be useful to most rusty_ache users. You may also want to point out the other projects that solved it better and which could serve as inspiration. + +## Attribution +This guide is based on the [contributing.md](https://contributing.md/generator)! From f26f70838d0dfab865b1966625210219e0b42b0f Mon Sep 17 00:00:00 2001 From: Ksenia Kotelnikova Date: Wed, 29 Oct 2025 22:16:27 +0300 Subject: [PATCH 03/10] ref: link fixes Signed-off-by: Ksenia Kotelnikova --- CONTRIBUTING.md | 28 ++++++++++++++-------------- 1 file changed, 14 insertions(+), 14 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index fb2ad44..2a07f4c 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -14,11 +14,11 @@ All types of contributions are encouraged and valued. See the [Table of Contents > If you want to ask a question, we assume that you have read the available [Documentation](https://github.com/p1onerka/rusty_ache/blob/main/README.md). -Before you ask a question, it is best to search for existing [Issues](https://github.com/p1onerka/rusty_ache/tree/main/issues) that might help you. In case you have found a suitable issue and still need clarification, you can write your question in this issue. +Before you ask a question, it is best to search for existing [Issues](https://github.com/p1onerka/rusty_ache/issues) that might help you. In case you have found a suitable issue and still need clarification, you can write your question in this issue. If you then still feel the need to ask a question and need clarification, we recommend the following: -- Open an [Issue](https://github.com/p1onerka/rusty_ache/tree/main/issues/new). +- Open an [Issue](https://github.com/p1onerka/rusty_ache/issues/new). - Provide as much context as you can about what you're running into. - Provide project and platform versions, depending on what seems relevant. @@ -37,13 +37,13 @@ A good bug report shouldn't leave others needing to chase you up for more inform - Make sure that you are using the latest version. - Determine if your bug is really a bug and not an error on your side e.g. using incompatible environment components/versions (Make sure that you have read the [documentation](https://github.com/p1onerka/rusty_ache/blob/main/README.md). If you are looking for support, you might want to check [this section](#i-have-a-question)). -- To see if other users have experienced (and potentially already solved) the same issue you are having, check if there is not already a bug report existing for your bug or error in the [bug tracker](https://github.com/p1onerka/rusty_ache/tree/main/issues?q=label%3Abug). +- To see if other users have experienced (and potentially already solved) the same issue you are having, check if there is not already a bug report existing for your bug or error in the bug tracker. - Collect information about the bug: -- Stack trace (Traceback) -- OS, Platform and Version (Windows, Linux, macOS, x86, ARM) -- Version of the compiler, SDK, runtime environment, depending on what seems relevant. -- Possibly your input and the output -- Can you reliably reproduce the issue? And can you also reproduce it with older versions? + - Stack trace (Traceback) + - OS, Platform and Version (Windows, Linux, macOS, x86, ARM). + - Version of the compiler, SDK, runtime environment, depending on what seems relevant. + - Possibly your input and the output. + - Can you reliably reproduce the issue? And can you also reproduce it with older versions? #### How Do I Submit a Good Bug Report? @@ -51,7 +51,7 @@ A good bug report shouldn't leave others needing to chase you up for more inform We use GitHub issues to track bugs and errors. If you run into an issue with the project: -- Open an [Issue](https://github.com/p1onerka/rusty_ache/tree/main/issues/new). +- Open an [Issue](https://github.com/p1onerka/rusty_ache/issues/new). - Explain the behavior you would expect and the actual behavior. - Please provide as much context as possible and describe the *reproduction steps* that someone else can follow to recreate the issue on their own. For good bug reports you should isolate the problem and create a reduced test case. - Provide the information you collected in the previous section. @@ -60,29 +60,29 @@ Once it's filed: - The project team will label the issue accordingly. - A team member will try to reproduce the issue with your provided steps. If there are no reproduction steps or no obvious way to reproduce the issue, the team will ask you for those steps. -- If the team is able to reproduce the issue, it will be marked `needs-fix`, as well as possibly other tags (such as `critical`), and the issue will be left to be [implemented by someone](#your-first-code-contribution). +- If the team is able to reproduce the issue, it will be marked `needs-fix`, as well as possibly other tags (such as `critical`), and the issue will be left to be implemented by someone. ### Suggesting Enhancements -This section guides you through submitting an enhancement suggestion for rusty_ache including completely new features and minor improvements to existing functionality. Following these guidelines will help maintainers and the community to understand your suggestion and find related suggestions. +This section guides you through submitting an enhancement suggestion for *rusty_ache* including completely new features and minor improvements to existing functionality. Following these guidelines will help maintainers and the community to understand your suggestion and find related suggestions. #### Before Submitting an Enhancement - Make sure that you are using the latest version. - Read the [documentation](https://github.com/p1onerka/rusty_ache/blob/main/README.md) carefully and find out if the functionality is already covered, maybe by an individual configuration. -- Perform a [search](https://github.com/p1onerka/rusty_ache/tree/main/issues) to see if the enhancement has already been suggested. If it has, add a comment to the existing issue instead of opening a new one. +- Perform a [search](https://github.com/p1onerka/rusty_ache/issues) to see if the enhancement has already been suggested. If it has, add a comment to the existing issue instead of opening a new one. - Find out whether your idea fits with the scope and aims of the project. It's up to you to make a strong case to convince the project's developers of the merits of this feature. Keep in mind that we want features that will be useful to the majority of our users and not just a small subset. If you're just targeting a minority of users, consider writing an add-on/plugin library. #### How Do I Submit a Good Enhancement Suggestion? -Enhancement suggestions are tracked as [GitHub issues](https://github.com/p1onerka/rusty_ache/tree/main/issues). +Enhancement suggestions are tracked as [GitHub issues](https://github.com/p1onerka/rusty_ache/issues). - Use a clear and descriptive title for the issue to identify the suggestion. - Provide a step-by-step description of the suggested enhancement in as many details as possible. - Describe the current behavior and explain which behavior you expected to see instead and why. At this point you can also tell which alternatives do not work for you. - You may want to include screenshots or screen recordings which help you demonstrate the steps or point out the part which the suggestion is related to. -- Explain why this enhancement would be useful to most rusty_ache users. You may also want to point out the other projects that solved it better and which could serve as inspiration. +- Explain why this enhancement would be useful to most *rusty_ache* users. You may also want to point out the other projects that solved it better and which could serve as inspiration. ## Attribution This guide is based on the [contributing.md](https://contributing.md/generator)! From c4a66374f56adcf13ad94387308811191e28b285 Mon Sep 17 00:00:00 2001 From: Ksenia Kotelnikova Date: Wed, 29 Oct 2025 23:16:49 +0300 Subject: [PATCH 04/10] feat: action for deploying docs Signed-off-by: Ksenia Kotelnikova --- .github/workflows/docs.yml | 34 ++++++++++++++++++++++++++++++++++ Cargo.toml | 5 +++++ 2 files changed, 39 insertions(+) create mode 100644 .github/workflows/docs.yml diff --git a/.github/workflows/docs.yml b/.github/workflows/docs.yml new file mode 100644 index 0000000..a74f3d8 --- /dev/null +++ b/.github/workflows/docs.yml @@ -0,0 +1,34 @@ +name: Deploy Documentation + +on: + push: + branches: [ main ] + pull_request: + branches: [ main ] + +jobs: + Build-And-Deploy: + if: github.event_name == 'push' && github.ref == 'refs/heads/main' + runs-on: ubuntu-latest + steps: + - uses: actions/checkout@v4 + + - name: Setup Rust + uses: actions-rs/toolchain@v1 + with: + toolchain: stable + override: true + components: rust-docs + + - name: Generate Documentation + run: | + cargo doc --no-deps --all-features + echo "" > target/doc/index.html + + - name: Deploy to GitHub Pages + uses: peaceiris/actions-gh-pages@v3 + with: + github_token: ${{ secrets.GITHUB_TOKEN }} + publish_dir: ./target/doc + publish_branch: docs + force_orphan: true \ No newline at end of file diff --git a/Cargo.toml b/Cargo.toml index 925f07e..19df84e 100644 --- a/Cargo.toml +++ b/Cargo.toml @@ -2,6 +2,8 @@ name = "rusty_ache" version = "0.1.0" edition = "2024" +documentation = "https://p1onerka.github.io/rusty_ache" +repository = "https://github.com/p1onerka/rusty_ache" [[bin]] name = "main" @@ -12,3 +14,6 @@ path = "src/bin/main.rs" image = "0.25.8" pixels = "0.15.0" winit = "0.30.12" + +[package.metadata.docs.rs] +all-features = true \ No newline at end of file From c0c5e2f905750ac6ce03b28e296408237e7002db Mon Sep 17 00:00:00 2001 From: Ksenia Kotelnikova Date: Wed, 29 Oct 2025 23:53:14 +0300 Subject: [PATCH 05/10] ref: add readme into CI for testing purposes Signed-off-by: Ksenia Kotelnikova --- .github/workflows/docs.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/workflows/docs.yml b/.github/workflows/docs.yml index a74f3d8..10e456b 100644 --- a/.github/workflows/docs.yml +++ b/.github/workflows/docs.yml @@ -8,7 +8,7 @@ on: jobs: Build-And-Deploy: - if: github.event_name == 'push' && github.ref == 'refs/heads/main' + if: github.event_name == 'push' && github.ref == 'refs/heads/main' || github.event_name == 'push' && github.ref == 'refs/heads/readme' # FOR TESTTING PURPOSES, DELETE BEFORE DEPLOY runs-on: ubuntu-latest steps: - uses: actions/checkout@v4 From 29ed94dcf43cc0ac93da6cb62bcd6d7710649362 Mon Sep 17 00:00:00 2001 From: Ksenia Kotelnikova Date: Thu, 30 Oct 2025 00:00:52 +0300 Subject: [PATCH 06/10] ref: change testing event to PR Signed-off-by: Ksenia Kotelnikova --- .github/workflows/docs.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/workflows/docs.yml b/.github/workflows/docs.yml index 10e456b..076181f 100644 --- a/.github/workflows/docs.yml +++ b/.github/workflows/docs.yml @@ -8,7 +8,7 @@ on: jobs: Build-And-Deploy: - if: github.event_name == 'push' && github.ref == 'refs/heads/main' || github.event_name == 'push' && github.ref == 'refs/heads/readme' # FOR TESTTING PURPOSES, DELETE BEFORE DEPLOY + if: github.event_name == 'push' && github.ref == 'refs/heads/main' || github.event_name == 'pull_request' && github.ref == 'refs/heads/readme' # FOR TESTTING PURPOSES, DELETE BEFORE DEPLOY runs-on: ubuntu-latest steps: - uses: actions/checkout@v4 From 43dc0083ef130f2d8736b01f0befc4b7f4c8e941 Mon Sep 17 00:00:00 2001 From: Ksenia Kotelnikova Date: Thu, 30 Oct 2025 00:02:43 +0300 Subject: [PATCH 07/10] ref: CI testing Signed-off-by: Ksenia Kotelnikova --- .github/workflows/docs.yml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/.github/workflows/docs.yml b/.github/workflows/docs.yml index 076181f..bad9ebe 100644 --- a/.github/workflows/docs.yml +++ b/.github/workflows/docs.yml @@ -2,13 +2,13 @@ name: Deploy Documentation on: push: - branches: [ main ] + branches: [ main, readme ] pull_request: - branches: [ main ] + branches: [ main, readme ] jobs: Build-And-Deploy: - if: github.event_name == 'push' && github.ref == 'refs/heads/main' || github.event_name == 'pull_request' && github.ref == 'refs/heads/readme' # FOR TESTTING PURPOSES, DELETE BEFORE DEPLOY + if: github.event_name == 'push' && github.ref == 'refs/heads/main' || github.event_name == 'push' && github.ref == 'refs/heads/readme' # FOR TESTTING PURPOSES, DELETE BEFORE DEPLOY runs-on: ubuntu-latest steps: - uses: actions/checkout@v4 From 197f7f2dcec204c4b3492e4e569e7ab43644adeb Mon Sep 17 00:00:00 2001 From: Ksenia Kotelnikova Date: Thu, 30 Oct 2025 00:11:28 +0300 Subject: [PATCH 08/10] ref: give the docs action permission to write Signed-off-by: Ksenia Kotelnikova --- .github/workflows/docs.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/.github/workflows/docs.yml b/.github/workflows/docs.yml index bad9ebe..07e09cb 100644 --- a/.github/workflows/docs.yml +++ b/.github/workflows/docs.yml @@ -6,6 +6,9 @@ on: pull_request: branches: [ main, readme ] +permissions: + contents: write + jobs: Build-And-Deploy: if: github.event_name == 'push' && github.ref == 'refs/heads/main' || github.event_name == 'push' && github.ref == 'refs/heads/readme' # FOR TESTTING PURPOSES, DELETE BEFORE DEPLOY From 40c2a2abe2cb9fa4cbdb71fa330ff913e273b5f8 Mon Sep 17 00:00:00 2001 From: Ksenia Kotelnikova Date: Thu, 30 Oct 2025 00:17:13 +0300 Subject: [PATCH 09/10] feat: add link to docs in README and CONTRIBUTING Signed-off-by: Ksenia Kotelnikova --- CONTRIBUTING.md | 6 +++--- README.md | 3 +++ 2 files changed, 6 insertions(+), 3 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 2a07f4c..689020f 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -12,7 +12,7 @@ All types of contributions are encouraged and valued. See the [Table of Contents ## I Have a Question -> If you want to ask a question, we assume that you have read the available [Documentation](https://github.com/p1onerka/rusty_ache/blob/main/README.md). +> If you want to ask a question, we assume that you have read the available [documentation](https://p1onerka.github.io/rusty_ache/rusty_ache/index.html). Before you ask a question, it is best to search for existing [Issues](https://github.com/p1onerka/rusty_ache/issues) that might help you. In case you have found a suitable issue and still need clarification, you can write your question in this issue. @@ -36,7 +36,7 @@ We will then take care of the issue as soon as possible. A good bug report shouldn't leave others needing to chase you up for more information. Therefore, we ask you to investigate carefully, collect information and describe the issue in detail in your report. Please complete the following steps in advance to help us fix any potential bug as fast as possible. - Make sure that you are using the latest version. -- Determine if your bug is really a bug and not an error on your side e.g. using incompatible environment components/versions (Make sure that you have read the [documentation](https://github.com/p1onerka/rusty_ache/blob/main/README.md). If you are looking for support, you might want to check [this section](#i-have-a-question)). +- Determine if your bug is really a bug and not an error on your side e.g. using incompatible environment components/versions (Make sure that you have read the [documentation](https://p1onerka.github.io/rusty_ache/rusty_ache/index.html). If you are looking for support, you might want to check [this section](#i-have-a-question)). - To see if other users have experienced (and potentially already solved) the same issue you are having, check if there is not already a bug report existing for your bug or error in the bug tracker. - Collect information about the bug: - Stack trace (Traceback) @@ -70,7 +70,7 @@ This section guides you through submitting an enhancement suggestion for *rusty_ #### Before Submitting an Enhancement - Make sure that you are using the latest version. -- Read the [documentation](https://github.com/p1onerka/rusty_ache/blob/main/README.md) carefully and find out if the functionality is already covered, maybe by an individual configuration. +- Read the [documentation](https://p1onerka.github.io/rusty_ache/rusty_ache/index.html) carefully and find out if the functionality is already covered, maybe by an individual configuration. - Perform a [search](https://github.com/p1onerka/rusty_ache/issues) to see if the enhancement has already been suggested. If it has, add a comment to the existing issue instead of opening a new one. - Find out whether your idea fits with the scope and aims of the project. It's up to you to make a strong case to convince the project's developers of the merits of this feature. Keep in mind that we want features that will be useful to the majority of our users and not just a small subset. If you're just targeting a minority of users, consider writing an add-on/plugin library. diff --git a/README.md b/README.md index 44a7369..6da3f6f 100644 --- a/README.md +++ b/README.md @@ -15,6 +15,9 @@ Run project: cargo run --bin main ``` +### Docs +Project documentation is availible [here](https://p1onerka.github.io/rusty_ache/rusty_ache/index.html). + ## Devs * [Aleksei Dmitrievstev](https://github.com/admitrievtsev) * [Ksenia Kotelnikova](https://github.com/p1onerka) From 608f67f8078ec068bc948aae1aa0b75a7a373523 Mon Sep 17 00:00:00 2001 From: Ksenia Kotelnikova Date: Thu, 30 Oct 2025 00:20:13 +0300 Subject: [PATCH 10/10] ref: delete testing from docs action Signed-off-by: Ksenia Kotelnikova --- .github/workflows/docs.yml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/.github/workflows/docs.yml b/.github/workflows/docs.yml index 07e09cb..b243bd9 100644 --- a/.github/workflows/docs.yml +++ b/.github/workflows/docs.yml @@ -2,16 +2,16 @@ name: Deploy Documentation on: push: - branches: [ main, readme ] + branches: [ main ] pull_request: - branches: [ main, readme ] + branches: [ main ] permissions: contents: write jobs: Build-And-Deploy: - if: github.event_name == 'push' && github.ref == 'refs/heads/main' || github.event_name == 'push' && github.ref == 'refs/heads/readme' # FOR TESTTING PURPOSES, DELETE BEFORE DEPLOY + if: github.event_name == 'push' && github.ref == 'refs/heads/main' runs-on: ubuntu-latest steps: - uses: actions/checkout@v4