We just published a walkthrough video showing all the steps to get a design ready for submission to the shuttle

I have done the whole process. Some observations. 1. If I push the changes into a branch that is not pulled into efabless workspace. Efabless workspace always pull the trunk/main. 2. Only three files - Makefile, LICENSE, README.md and two directories - gds, verilog/gl are enough to pass prechecks in efabless platform. 3. gds directory must contain user_project_wrapper.gds.gz and <your design>.gds.gz. No other files need in this directory 4. verilog/gl directories must contain the gate level netlists (not RTL) user_project_wrapper.v and <your design>.v 5. I have not changed any of the macro.cfg files 6. Adding testbecnches and passing it, does not affect the precheck and tapeout. Because they check only gds files. 7. To make user_project_wrapeer I have changed only 3 things VERILOG_FILES_BLACKBOX, EXTRA_GDS_FILES, EXTRA_LEFS. Nothing else. With all these I was able to pass the precheck and tapeout in efabless platform (website). Want to know if my design will be selected...🤞

If I push the changes into a branch that is not pulled into efabless workspace. Efabless workspace always pull the trunk/main.

I've found this to be inconvenient too. Adding an optional branch or tag to the efabless config page would be nice.

I've found the easiest thing is set the default branch in GitHub.