Skip to content

updated report#78

Merged
palisadoes merged 1 commit intoPalisadoesFoundation:mainfrom
VanshikaSabharwal:report-update
Oct 26, 2025
Merged

updated report#78
palisadoes merged 1 commit intoPalisadoesFoundation:mainfrom
VanshikaSabharwal:report-update

Conversation

@VanshikaSabharwal
Copy link
Copy Markdown
Contributor

What kind of change does this PR introduce?

Documentation update — added mentee report for 2025 program.

Issue Number:

N/A

Did you add tests for your changes?

Not applicable (documentation update only).

Snapshots/Videos:

N/A

If relevant, did you update the documentation?

Yes, added my mentee report markdown under the mentee reports directory.

Summary

This PR adds my final mentee report for the 2025 internship with The Palisadoes Foundation.
The report includes an overview of my project — API Improvement and Stability of the Backend to Handle Heavy Traffic (Permanent CORS Fix) — along with completed work, challenges faced, lessons learned, and conclusions.

Does this PR introduce a breaking change?

No, this PR only adds a new markdown file for documentation.

Other information

The report documents all key PRs, deployments, and project outcomes achieved during my internship period.

Have you read the contributing guide?

Yes

@github-actions
Copy link
Copy Markdown

Our Pull Request Approval Process

Thanks for contributing!

Testing Your Code

Remember, your PRs won't be reviewed until these criteria are met:

  1. We don't merge PRs with poor code quality.
    1. Follow coding best practices such that CodeRabbit.ai approves your PR.
  2. We don't merge PRs with failed tests.
    1. When tests fail, click on the Details link to learn more.
    2. Write sufficient tests for your changes (CodeCov Patch Test). Your testing level must be better than the target threshold of the repository
    3. Tests may fail if you edit sensitive files. Ask to add the ignore-sensitive-files-pr label if the edits are necessary.
  3. We cannot merge PRs with conflicting files. These must be fixed.

Our policies make our code better.

Reviewers

Do not assign reviewers. Our Queue Monitors will review your PR and assign them.
When your PR has been assigned reviewers contact them to get your code reviewed and approved via:

  1. comments in this PR or
  2. our slack channel

Reviewing Your Code

Your reviewer(s) will have the following roles:

  1. arbitrators of future discussions with other contributors about the validity of your changes
  2. point of contact for evaluating the validity of your work
  3. person who verifies matching issues by others that should be closed.
  4. person who gives general guidance in fixing your tests

CONTRIBUTING.md

Read our CONTRIBUTING.md file. Most importantly:

  1. PRs with issues not assigned to you will be closed by the reviewer
  2. Fix the first comment in the PR so that each issue listed automatically closes

Other

  1. 🎯 Please be considerate of our volunteers' time. Contacting the person who assigned the reviewers is not advised unless they ask for your input. Do not @ the person who did the assignment otherwise.
  2. Read the CONTRIBUTING.md file make

@palisadoes palisadoes merged commit 3b111ac into PalisadoesFoundation:main Oct 26, 2025
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants