diff --git a/about.html b/about.html index 349cec82..741862c8 100644 --- a/about.html +++ b/about.html @@ -17,7 +17,7 @@

About Us

MarkBind is a project based in National University of Singapore, School of Computing, and is funded by an education grant from NUS Center for Development of Teaching and Learning.

You can email us at markbind at comp.nus.edu.sg

Interested in contributing to MarkBind? Visit the MarkBind project on GitHub.

Contributors ✨

Mentors:

Dev Team:

Thanks goes to these wonderful people (emoji key):


Past Members:

+

About Us

MarkBind is a project based in National University of Singapore, School of Computing, and is funded by an education grant from NUS Center for Development of Teaching and Learning.

You can email us at markbind at comp.nus.edu.sg

Interested in contributing to MarkBind? Visit the MarkBind project on GitHub.

Contributors ✨

Mentors:

Dev Team:

Thanks goes to these wonderful people (emoji key):


Past Members:

diff --git a/devGuide/index.page-vue-render.js b/devGuide/index.page-vue-render.js index 48d3e15e..cbeca875 100644 --- a/devGuide/index.page-vue-render.js +++ b/devGuide/index.page-vue-render.js @@ -5,6 +5,6 @@ with(this){return _c('div',{attrs:{"id":"app"}},[_c('header',{attrs:{"sticky":"" }; var pageVueStaticRenderFns = [function anonymous( ) { -with(this){return _c('div',[_c('footer',[_c('div',{staticClass:"text-center"},[_c('small',[_v("[Generated by "),_c('a',{attrs:{"href":"https://markbind.org/"}},[_v("MarkBind 5.3.0")]),_v(" on Fri, 22 Mar 2024, 5:24:08 UTC]")]),_c('br'),_v(" "),_c('small',[_v("This site is powered by "),_c('a',{attrs:{"href":"https://www.netlify.com/"}},[_v("Netlify")]),_v(".")])])])])} +with(this){return _c('div',[_c('footer',[_c('div',{staticClass:"text-center"},[_c('small',[_v("[Generated by "),_c('a',{attrs:{"href":"https://markbind.org/"}},[_v("MarkBind 5.3.0")]),_v(" on Fri, 22 Mar 2024, 5:26:01 UTC]")]),_c('br'),_v(" "),_c('small',[_v("This site is powered by "),_c('a',{attrs:{"href":"https://www.netlify.com/"}},[_v("Netlify")]),_v(".")])])])])} }]; \ No newline at end of file diff --git a/devGuide/projectManagement.html b/devGuide/projectManagement.html index 2ec9ba82..41b054bb 100644 --- a/devGuide/projectManagement.html +++ b/devGuide/projectManagement.html @@ -51,7 +51,7 @@ <meta name="viewport" content="width=device-width, initial-scale=1"> <title>Open Bugs</title> <link rel="stylesheet" href="../markbind/css/bootstrap.min.css"> -

If any other lines changed, that likely means the functional tests weren't updated in a pull request. Do revert everything done so far, and make a pull request specifically to fix that first!

  • If core-web package bundle was updated earlier: also ensure that the updated bundles are copied to each of the expected test site's folders.

    • We do this for each MarkBind release (rather than require contributors to update the bundles for each affected PR), in order to reduce unnecessary merge conflicts. It also makes it easier for the maintainers to vet the changes.
    • Typically, the bundle will be updated automatically in the expected test site's folders after running npm run updatetest in the previous step.
  • Combine the changes that you made in the last two steps with the version commit generated by lerna version. To do so, amend the version commit and version tag by doing the following — take note to change vA.B.C to the new version.

    $ git commit -a --amend --reuse-message vA.B.C
     $ git tag --force vA.B.C     # to reassign the tag to the newly amended commit
    -
  • Push the new commit and version tag generated by npm (change vA.B.C to the new version's string accordingly).

    $ git push upstream master
     $ git push upstream vA.B.C
    -
  • Publish by running npx lerna publish from-git. You should receive a notification by npm that the publish is successful.

  • Smoke test the new version by installing the new version (run npm i -g markbind-cli@A.B.C) and playing around with it a bit to ensure that it works.

    • If you used npm link for your project, ensure that you try the new release on another platform that doesn't use npm link, so that we can be sure the end-users can install and use the new version.
    • You can also try the new release on a project that uses MarkBind as a local dev-dependency.
  • Verify the website at markbind.org has been updated. For example, you can look at the footer of the website to see if the version number is updated.

    Note that it may take a few minutes for the website to be updated and you may need to check it in an incognito window to avoid caching.

    The deployment is automated. However, if it doesn't deploy properly for the release, do the following:

    $ npm run deploy:ug
    -
  • The senior dev approves and merge the automatic PR.
  • The senior dev deletes the automatic PR.
  • Note that:

    GitHub Actions: markbind-reusable-workflows

    Appendix: Style guides


    +

    GitHub Actions: markbind-reusable-workflows

    Appendix: Style guides