Closed CAMOBAP closed 5 months ago
@ronaldtse To me it seems that due to maintainability (common.env duplication), it's better to keep setup-tebako
in the tebako
repo
@maxirmx how do you think?
@CAMOBAP I guess. I can get rid of common.env. I have another possible issue in mind - setup-tebako will depend on tebako, so if tebako workflow uses setup-tebako action it will create a circular dependency that will be hard to maintain.
Let's keep it in the same repo for now. I suggest will look at the options to simplify setup first.
@CAMOBAP how about we make a new "setup-tebako" repo just like the Fontist one?