Skip to content

Commit 71a9756

Browse files
authored
Fix "have a PR merged" heading links (#439)
1 parent cd5e653 commit 71a9756

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

_posts/2025-02-28-gsoc2025.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -66,7 +66,7 @@ In short:
6666
1. [Agree to be bound by our Code of Conduct](#code-of-conduct) (and [WESTPA's Code of Conduct](https://github.com/westpa/westpa/wiki/Code-of-Conduct) if you are applying for a WESTPA collaboration project [i.e., [Project 1]({{ site.github.wiki }}/GSoC-2025-Project-Ideas#project-1-integrating-mdanalysis-streaming-analysis-within-westpa-propagators), [Project 2]({{ site.github.wiki }}/GSoC-2025-Project-Ideas#project-2-dashboard-for-tracking-westpa-simulation-progress)]);
6767
2. [Familiarize yourself with MDAnalysis and relevant partner projects](#familiarize-yourself-with-mdanalysis-and-relevant-partner-projects);
6868
3. [Submit a short pre-proposal](#submit-a-pre-proposal)
69-
4. **If you have been invited to proceed with your application (based on your pre-proposal)** [have a pull request merged](#have-a-pull-request-merged-if-you-are-invited-to-based-on-your-pre-proposal) in MDAnalysis or a partner organization.
69+
4. **If you have been invited to proceed with your application (based on your pre-proposal)** [have a pull request merged](#have-a-pull-request-merged-by-invitation) in MDAnalysis or a partner organization.
7070

7171
### Code of Conduct
7272

@@ -109,7 +109,7 @@ As some of the [project ideas][ideas] represent collaboration between MDAnalysis
109109

110110
We ask you to submit a short *pre-proposal* so that we can evaluate your understanding of the proposed project. In this pre-proposal you tell us what project you’d like to work on, what you consider the major challenges, and how you plan to solve the problem. MDAnalysis developers will review your proposal and then either invite you to continue with your application and work on an issue to get involved in the code development or tell you that we will not consider your application. *Please note that this decision is final, and applicants should only submit **one** pre-proposal.* A rejection is not a judgment on you or your abilities but an assessment of how well you fit the specific requirements of MDAnalysis as a scientific software package — we much rather you spend your energies on contributing to another exciting GSoC project than being rejected later by MDAnalysis.
111111

112-
**We require GSoC applicants to submit a pre-proposal** that will determine who is then invited to [contribute a pull request for evaluation](#have-a-pull-request-merged-if-you-are-invited-to-based-on-your-pre-proposal) (see below). If you are invited to contribute a pull request and ultimately submit a full application, the pre-proposal will help you gather some of the information you will need to include.
112+
**We require GSoC applicants to submit a pre-proposal** that will determine who is then invited to [contribute a pull request for evaluation](#have-a-pull-request-merged-by-invitation) (see below). If you are invited to contribute a pull request and ultimately submit a full application, the pre-proposal will help you gather some of the information you will need to include.
113113

114114
Submit your pre-proposal via [this submission form][submission form] **as soon as possible, but no later than March 21, 2025**. You should prepare the following information for your pre-proposal:
115115
* Email address

0 commit comments

Comments
 (0)