Neurips, how can i submit the "link" to the code? [D]

NeurIPS submissions are a tightrope walk between rigorous scientific presentation and practical accessibility. When a researcher wonders whether they can simply attach a PDF that contains a hyperlink to their code, the question cuts to the core of how the community balances reproducibility with the constraints of conference workflows. In the same vein that a purchasing form developer might look to an Order form that references data from a table to streamline workflow, or a Java engineer might follow the nuances of JEP 533 Tightens Exception Handling in Java's Structured Concurrency for JDK 27 to keep code robust, authors must navigate NeurIPS’s supplementary material guidelines. The crux is that the supplementary section is designed for raw data, code, and additional figures—not for clickable links embedded within a PDF. The conference platform parses uploaded files in a specific format; it does not execute or render hyperlinks, which means a PDF link will be ignored or flagged as non-compliant.

Why does this matter? Because reproducibility is the lifeblood of machine learning research. When code is tucked away behind a PDF, reviewers cannot quickly validate results, and the broader community loses an opportunity to build upon the work. By contrast, submitting code through a dedicated platform such as GitHub, Bitbucket, or a preprint archive, and then referencing that link explicitly in the main paper, ensures that reviewers and readers can access the exact implementation without friction. It also signals that the author values transparency and invites collaboration. The supplementary section can still host essential artifacts—model checkpoints, synthetic datasets, or extended proofs—but the entry point should be a reliable, version-controlled repository.

The practical workaround is straightforward. First, upload your code to a public repository and pin the commit that corresponds to the manuscript. Then, in the main LaTeX file, add a line such as “The code is available at https://github.com/author/repo/tree/commit-id.” NeurIPS’s submission portal will accept this as a text field and will cross‑check the URL for accessibility. If you must include the link in the supplementary material, use plain text rather than a hyperlink: “See our GitHub repository at https://github.com/author/repo.” This approach satisfies the platform’s constraints while keeping the link discoverable. It also aligns with the conference’s emphasis on reproducible research, which is increasingly becoming a formal requirement for acceptance.

Beyond the mechanics, this issue reflects a broader shift in how academic communities handle supplementary information. Traditional journals allowed authors to attach PDFs with embedded links, but the rise of open science mandates that links be live and persistent. By enforcing a text‑only supplementary policy, NeurIPS nudges researchers toward more sustainable practices—embedding code in version control, using DOI‑registered datasets, and providing clear installation instructions. These practices not only improve the paper’s credibility but also enhance its long‑term utility. As machine learning models grow in complexity, the barrier to reproducing results rises; simplifying the submission process for code access is a small but significant step toward lowering that barrier.

Looking ahead, we can anticipate that conferences will further refine their policies to accommodate emerging formats like Jupyter notebooks or interactive demos. The question for authors is whether they will adapt early, or risk falling behind as the community’s expectations evolve. Will the next iteration of NeurIPS require a dedicated “Code and Data” portal, or will it embrace containerized environments that encapsulate the entire experiment? The answer will shape how researchers approach reproducibility in the years to come, and will determine whether the field continues to prioritize accessibility alongside innovation.