Skip to content

Update version to 2.0.1-preview#44

Closed
josesimoes wants to merge 1 commit into
developfrom
josesimoes-patch-1
Closed

Update version to 2.0.1-preview#44
josesimoes wants to merge 1 commit into
developfrom
josesimoes-patch-1

Conversation

@josesimoes

Copy link
Copy Markdown
Member

Description

Motivation and Context

  • Just grabing the native stubs.

How Has This Been Tested?

Screenshots

Types of changes

  • Improvement (non-breaking change that improves a feature, code or algorithm)
  • Bug fix (non-breaking change which fixes an issue with code or algorithm)
  • New feature (non-breaking change which adds functionality to code)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Config and build (change in the configuration and build system, has no impact on code or features)
  • Dependencies (update dependencies and changes associated, has no impact on code or features)
  • Unit Tests (add new Unit Test(s) or improved existing one(s), has no impact on code or features)
  • Documentation (changes or updates in the documentation, has no impact on code or features)

Checklist:

  • My code follows the code style of this project (only if there are changes in source code).
  • My changes require an update to the documentation (there are changes that require the docs website to be updated).
  • I have updated the documentation accordingly (the changes require an update on the docs in this repo).
  • I have read the CONTRIBUTING document.
  • I have tested everything locally and all new and existing tests passed (only if there are changes in source code).
  • I have added new tests to cover my changes.

@nfbot nfbot left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🤖 Hey @josesimoes, your PR description doesn't match our PR template and that breaks our auto-labeling.

Here's what's off:

  • ✏️ Section ## Description is empty — please fill it in.
  • ☑️ At least one item under ## Types of changes must be ticked ([x]).

Please paste the template from the link above and fill it in — keep all the checkbox lines even if they don't apply (just leave them unticked). 🙏

🤖 Prompt for fixing with AI agents
You are fixing a GitHub pull request description that failed the nanoFramework PR template check.
Rewrite the PR body so that it strictly matches the template at https://github.com/nanoframework/.github/blob/main/PULL_REQUEST_TEMPLATE.md (variant: "OrgDefault").

Rules:
1. Keep these top-level headings, in this order: ## Description, ## Motivation and Context, ## Types of changes, ## Checklist.
2. The `## Types of changes` section MUST contain ALL of these checkbox lines (verbatim), ticked only when they apply:
   - [ ] Improvement (...)
   - [ ] Bug fix (...)
   - [ ] New feature (...)
   - [ ] Breaking change (...)
   - [ ] Config and build (...)
   - [ ] Dependencies (...)
   - [ ] Unit Tests (...)
   - [ ] Documentation (...)
3. The `## Checklist` section MUST contain ALL of these checkbox lines (verbatim), ticked only when they apply:
   - [ ] My code follows the code style of this project ...
   - [ ] My changes require an update to the documentation ...
   - [ ] I have updated the documentation accordingly ...
   - [ ] I have read the ...
   - [ ] I have tested everything locally ...
   - [ ] I have added new tests to cover my changes ...
4. `## Description` must be non-empty. `## Motivation and Context` may be empty when there's nothing extra to add.
5. Do NOT invent new facts — preserve whatever real content the author already wrote.
6. Do NOT remove checkbox lines just because they don't apply; leave them unticked.

Specifically, fix these issues:
- Empty section: ## Description
- No Types-of-changes item is ticked; tick the applicable ones.

Output ONLY the new PR body in markdown — no fences, no commentary.

@coderabbitai

coderabbitai Bot commented Jul 3, 2026

Copy link
Copy Markdown

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository: nanoframework/coderabbit/.coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: 504f403d-5b23-478d-863d-02cd5a4aeacc

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@josesimoes josesimoes closed this Jul 3, 2026
@josesimoes josesimoes deleted the josesimoes-patch-1 branch July 3, 2026 13:11
@nfbot nfbot added the invalid This doesn't seem right label Jul 3, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

invalid This doesn't seem right

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants