Skip to content

[3.0] Ensure consistent usage of Silk.NET and version numbers - #2636

Open
Exanite wants to merge 3 commits into
develop/3.0from
feature/branding-consistency-and-docs-edits
Open

Exanite wants to merge 3 commits into
develop/3.0from
feature/branding-consistency-and-docs-edits

Conversation

@Exanite

@Exanite Exanite commented Nov 7, 2026 •

Copy link
Copy Markdown
Member

Summary of the PR

This PR updates docs and doc comments to consistently use Silk.NET instead of Silk, 3.X instead of 3.x, and similar.

  • I confirm that I am the author of this code and release it to the Silk.NET project under the MIT license. This contribution does not contain code from other sources, including code generated by a Large Language Model ("AI").

Related issues, Discord discussions, or proposals

This was discussed here: https://discord.com/channels/521092042781229087/587346162802229298/1568654496379441183

Further Comments

I noticed that I explained profiles and source sets wrong back when I originally wrote the generator docs. I'll open a separate PR to fix this. This turned out to be a trivial change.

Tasks

  • Ensure consistent branding
    • Use Silk.NET over Silk
    • Use capitalized 3.X/2.X instead of 3.x, etc
  • Also fix other minor issues I spotted
  • Fix my explanation of source sets and profiles in the generator docs

@Exanite
Exanite force-pushed the feature/branding-consistency-and-docs-edits branch from 3d77844 to bc11e56 Compare November 7, 2026 19:29
@Exanite

Exanite commented Nov 7, 2026

Copy link
Copy Markdown
Member Author

Force push was to rebase onto develop/3.0.

@github-actions

github-actions Bot commented Nov 7, 2026

Copy link
Copy Markdown
Contributor

Silk.NET bindings regeneration reminder

Some of the bindings are likely affected by this PR.
Please regenerate these by posting a comment with /bindings OpenAL OpenCL OpenGL OpenXR SDL Vulkan.

If you believe this to be in error, then please write a comment explaining why and ignore this reminder.

@Exanite
Exanite marked this pull request as ready for review November 7, 2026 19:32
@Exanite
Exanite requested a review from a team as a code owner November 7, 2026 19:32
@Exanite
Exanite marked this pull request as draft November 7, 2026 19:35
@github-actions

github-actions Bot commented Nov 7, 2026 •

Copy link
Copy Markdown
Contributor

File Coverage
All files 22% ✅

Minimum allowed coverage is 0%

Generated by 🐒 cobertura-action against 9fccc98

@Exanite
Exanite marked this pull request as ready for review November 7, 2026 19:50

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Todo

Development

Successfully merging this pull request may close these issues.

1 participant