Files
ioccc/how-to-bugfix.md
T
Landon Curt Noll ac41f07a83 move fix thanks a file, update top level html links, rename CONTRIBUTING.md
The fix thank you's have been moved from `README.md` to
`thanks-for-fixes.md`.

**WARNING**: Some mistakes may have been made in doing this.
We presume later changes by others will correct any issues.

The `CONTRIBUTING.md` was renamed `how-to-enter.md`.

A 3rd line of links was added to top level html such as
`contact.html`, `index.html`, `judges.html`, `winners.html`,
and `years.html`.

Improved blank line use in a number (but not all) `README.md` files.
2023-06-06 16:59:53 -07:00

1.5 KiB

How to fix an IOCCC entry

If you see a problem with an IOCCC entry, first check the known bugs file. In some cases what you might think of as a bug is instead a known feature. On some cases the bug is known, but no fix has ever been submitted. In other cases you may have found a new problem.

If you do have a fix, and the known bugs file does not recommend against fixing it, then please opening a GitHub pull request against the master branch of the ioccc-src/winner repo repo.

BTW: A problem is not limited to the code itself. Fixing typos in files such as "README.md" files, fixing issues in a "Makefile", or otherwise correcting an IOCCC winner is VERY MUCH WELCOME! Please use the same GitHub pull request process against the master branch of the ioccc-src/winner repo repo.

Please help us fix typos and / or otherwise improve the write-up of how IOCCC winning entries are presented!

And of course, an IOCCC winner's may update their own entries (metadata as well as source code and any extra files) by opening a GitHub pull request against the master branch of the ioccc-src/winner repo repo. e