Skip to content

docs: fix incorrect project numbering in GSoC 2026 portal#4346

Open
assu-2000 wants to merge 1 commit intokubeflow:masterfrom
assu-2000:master
Open

docs: fix incorrect project numbering in GSoC 2026 portal#4346
assu-2000 wants to merge 1 commit intokubeflow:masterfrom
assu-2000:master

Conversation

@assu-2000
Copy link
Copy Markdown

Corrected inconsistent numbering across project listings.

Ensures proper alignment between project IDs and titles for accurate referencing.

Description of Changes

  • Renumbered project entries to ensure sequential consistency
  • Fixed mismatches between project numbers and titles
  • Verified alignment across the entire GSoC 2026 project list

Related Issues

N/A (no associated issue)

Why this matters

Accurate project numbering is important for:

  • Referencing projects in GSoC proposals
  • Avoiding confusion for contributors and applicants
  • Maintaining documentation quality and consistency

Checklist

  • You have signed off your commits
  • Ensure you follow best practices from our contributing guide
  • (for big changes) I will post screenshots of the changes in a PR comment

Corrected inconsistent numbering across project listings.

Ensures proper alignment between project IDs and titles for accurate referencing.

Signed-off-by: assurance mbula  <71324454+assu-2000@users.noreply.github.com>
@google-oss-prow google-oss-prow bot added the area/community AREA: Community Docs label Mar 19, 2026
@google-oss-prow google-oss-prow bot requested a review from jbottum March 19, 2026 15:04
@google-oss-prow
Copy link
Copy Markdown

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign akgraner for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@google-oss-prow
Copy link
Copy Markdown

Hi @assu-2000. Thanks for your PR.

I'm waiting for a kubeflow member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@github-actions
Copy link
Copy Markdown

🚫 This command cannot be processed. Only organization members or owners can use the commands.

Copy link
Copy Markdown
Member

@Arhell Arhell left a comment

Choose a reason for hiding this comment

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

/ok-to-test

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

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants