- # However, if you remove everything, the rebase will be aborted.</code></pre><p>Then in the next screen that appears, we can just delete all messages that we do not want to show in the commit. After this is done and we are back to the console, we have to force push. We need to force push because we rewrote the local commit history.</p><pre><code class="nohighlight hljs">$ git push -u origin <name_of_local_branch> --force</code></pre><p>You can find more information about squashing <a href="https://github.com/edx/edx-platform/wiki/How-to-Rebase-a-Pull-Request#squash-your-changes">here</a>.</p><h3 id="Unit-testing"><a class="docs-heading-anchor" href="#Unit-testing">Unit testing</a><a id="Unit-testing-1"></a><a class="docs-heading-anchor-permalink" href="#Unit-testing" title="Permalink"></a></h3><p>Currently a number of checks are run per commit for a given PR.</p><ul><li><code>JuliaFormatter</code> checks if the PR is formatted with <code>.dev/climaformat.jl</code>.</li><li><code>Documentation</code> rebuilds the documentation for the PR and checks if the docs are consistent and generate valid output.</li><li><code>Unit Tests</code> run subsets of the unit tests defined in <code>tests/</code>, using <code>Pkg.test()</code>. The tests are run in parallel to ensure that they finish in a reasonable time. The tests only run the latest commit for a PR, branch and will kill any stale jobs on push. These tests are only run on linux (Ubuntu LTS).</li></ul><p>Unit tests are run against every new commit for a given PR, the status of the unit-tests are not checked during the merge process but act as a sanity check for developers and reviewers. Depending on the content changed in the PR, some CI checks that are not necessary will be skipped. For example doc only changes do not require the unit tests to be run.</p><h3 id="The-merge-process"><a class="docs-heading-anchor" href="#The-merge-process">The merge process</a><a id="The-merge-process-1"></a><a class="docs-heading-anchor-permalink" href="#The-merge-process" title="Permalink"></a></h3><p>We ensure that all unit tests across several environments, Documentation builds, and integration tests (managed by Buildkite), pass before merging any PR into <code>main</code>. The integration tests currently run some of our example cases in <code>examples/</code>.</p></article><nav class="docs-footer"><a class="docs-footer-prevpage" href="../installation_instructions/">« Installation instructions</a><a class="docs-footer-nextpage" href="../examples/sinusoid_example/">Simple example walkthrough »</a><div class="flexbox-break"></div><p class="footer-message">Powered by <a href="https://github.com/JuliaDocs/Documenter.jl">Documenter.jl</a> and the <a href="https://julialang.org/">Julia Programming Language</a>.</p></nav></div><div class="modal" id="documenter-settings"><div class="modal-background"></div><div class="modal-card"><header class="modal-card-head"><p class="modal-card-title">Settings</p><button class="delete"></button></header><section class="modal-card-body"><p><label class="label">Theme</label><div class="select"><select id="documenter-themepicker"><option value="auto">Automatic (OS)</option><option value="documenter-light">documenter-light</option><option value="documenter-dark">documenter-dark</option><option value="catppuccin-latte">catppuccin-latte</option><option value="catppuccin-frappe">catppuccin-frappe</option><option value="catppuccin-macchiato">catppuccin-macchiato</option><option value="catppuccin-mocha">catppuccin-mocha</option></select></div></p><hr/><p>This document was generated with <a href="https://github.com/JuliaDocs/Documenter.jl">Documenter.jl</a> version 1.16.0 on <span class="colophon-date" title="Monday 19 January 2026 04:04">Monday 19 January 2026</span>. Using Julia version 1.11.8.</p></section><footer class="modal-card-foot"></footer></div></div></div></body></html>
0 commit comments