keepcalculator

06 Numbers and Powers

Gemini Hack Kigali: What Stayed After the Pull Requests

Card No. 06·83084 · Updated · Standard formula, shown below

The Gemini Hack Kigali pull requests that were merged into the main repository stayed as permanent code contributions, while those that were not merged remained as open pull requests or were closed without integration. In short, the merged pull requests became part of the project’s codebase, and the unmerged ones did not change the official repository. This article explains what happens to pull requests after a hackathon, what the organizers and maintainers typically do with them, and what participants should expect.

What Happens to Pull Requests After a Hackathon

After a hackathon like Gemini Hack Kigali, the pull requests (PRs) submitted by participants go through a triage process. The maintainers of the repository review each PR for code quality, test coverage, and alignment with the project’s roadmap. Some PRs are merged immediately, some are marked as “changes requested” and require the author to make updates, and others are closed if they are duplicates, incomplete, or out of scope. The merged PRs become part of the official codebase, and their changes are visible in the repository’s history. The unmerged PRs remain in the pull request queue unless the author or maintainer closes them.

The Review Process for Hackathon PRs

Maintainers of open-source projects often treat hackathon PRs with extra care because they come from new contributors. The review process typically includes:

  • Checking that the code follows the project’s style guide and linting rules.
  • Running automated tests to ensure the changes don’t break existing functionality.
  • Verifying that the PR addresses an issue or adds a feature that the maintainers actually want.
  • Requesting changes if the code has bugs, lacks documentation, or needs refactoring.

For a hackathon like Gemini Hack Kigali, the organizers often coordinate with the maintainers to encourage them to review PRs promptly. But the final decision always rests with the maintainers, not the hackathon organizers.

What Stays: Merged Code and Its Impact

When a PR is merged, the changes become part of the repository’s main branch. That means the code is now in the official version of the project. The impact of merged code can be significant: it may add a new feature, fix a bug, or improve performance. For example, if a participant submitted a PR that adds a new API endpoint, that endpoint is now live for all users of the project. The merged code also stays in the repository’s history, so it can be traced back to the hackathon and the contributor.

What Stays: The Contributor’s Record

Even if a PR is not merged, the pull request itself stays on GitHub as a record of the contributor’s work. This is important for the contributor’s portfolio. A pull request that is well-written but not merged still shows that the person can read a codebase, write code, and communicate with maintainers. Many employers and open-source communities look at a person’s pull request history, not just their merged commits. So even an unmerged PR can stay as a valuable artifact of participation.

Common Reasons PRs Are Not Merged

There are several common reasons why a hackathon PR might not be merged:

  • The PR is a duplicate of an existing pull request or issue.
  • The code has bugs or fails tests.
  • The PR is too large and hard to review.
  • The feature is not aligned with the project’s roadmap.
  • The contributor did not respond to review feedback after the hackathon ended.

It’s also possible that the maintainers simply don’t have time to review all hackathon PRs. In that case, the PR stays open indefinitely. Participants can follow up politely to ask about the status, but they should not expect a merge just because they participated.

What Participants Should Do After the Hackathon

If you submitted a PR at Gemini Hack Kigali and want to increase the chances of it being merged, here are steps you can take:

  1. Check the status of your PR on GitHub. If it says “changes requested,” read the reviewer’s comments carefully.
  2. Make the requested changes and push them to your branch. This updates the PR automatically.
  3. Add a comment on the PR to let the maintainer know you’ve addressed their feedback.
  4. If the PR is closed, ask politely if you can reopen it or if there’s a better way to contribute.
  5. If the PR is still open but no one has responded, wait a few weeks, then send a friendly follow-up comment.

Remember that maintainers are often volunteers. A polite, patient approach works better than demanding a merge.

How to Turn an Unmerged PR into Something Useful

If your PR wasn’t merged, you can still make it useful. Fork the repository and keep your changes in your own branch. That way, you have a working version of the feature you built. You can also write a blog post about your experience, share the code on your portfolio, or use it as a starting point for a personal project. The skills you demonstrated in the PR are real, even if the maintainers didn’t accept it.

Frequently Asked Questions

Do hackathon PRs get merged automatically?

No. Hackathon PRs go through the same review process as any other PR. The maintainers decide whether to merge based on code quality, usefulness, and fit with the project. A hackathon does not guarantee a merge.

What if my PR is still open after months?

That’s common. Maintainers may be busy or the PR may be waiting for a decision. You can leave a polite comment asking for a status update. If there’s no response after a few more weeks, it’s reasonable to assume the PR won’t be merged.

Can I submit the same PR to another project?

Yes, if the code is your own and the license allows it. But make sure the other project actually needs the feature. Copying a PR to many projects without checking is not good practice.

Does an unmerged PR look bad on my GitHub profile?

No. An unmerged PR shows that you attempted to contribute and went through the process. Many contributors have unmerged PRs. What matters is the quality of your work and how you handle feedback.

Who owns the code in a hackathon PR?

The contributor owns the copyright to their code, but by submitting a PR to a repository, they are typically granting the project the right to use it under the project’s license. The exact terms depend on the license and any agreements signed at the hackathon.

What happens to the winning PRs from Gemini Hack Kigali?

Winning PRs are usually merged if they meet the project’s standards. But even a winning PR might be merged later after some adjustments. The hackathon prize is for the work, not a guarantee of merge.

Related

Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.

More cards in this drawer

The whole Numbers and Powers drawer →