Closed domlimm closed 2 years ago
@domlimm Yes, basically, ensure that GitHub has the latest code of your v1.4
(that matches the PDF and JAR files that you uploaded to LumiNUS) and the code is divided correctly among the team members (as shown by the code dashboard).
Hi @damithc , if I already created a v1.4 release on github, but later made minor edits to my UG and DG (no code at all) before submitting to LumiNus, do I need to delete my old v1.4 release and create a new v1.4 release based on the newest commit before uploading to luminus?
Hi @damithc , if I already created a v1.4 release on github, but later made minor edits to my UG and DG (no code at all) before submitting to LumiNus, do I need to delete my old v1.4 release and create a new v1.4 release based on the newest commit before uploading to luminus? @bingsen0806 You can do another release e.g.,
v1.4.1
while keeping the previous. You can create the release after uploading to LumiNUS
@damithc noted on it! thanks prof!
@bingsen0806 closing the issue as prof has answered your query too!
Hello prof, may I ask what does this mean?
Is it related to the team's release for
v1.4
?Thank you!