You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is the version.txt file generated manually? And if yes, which initial version should I use for the dashboard project?
Should I also integrate the release-tags functionality? Or are we focusing on the alpha tags only at this moment?
I see the create-build.yml already exists, should I change its name, or modify it somehow, because it seems that this script already creates the required image, am I right?
Should I also implement the actual tests workflow? And if yes, what should it include? I'm imagining Karma UTs/configuration, anything else? (although it seems we don't have any tests currently for the dashboard)
@TFphoenix While @giobart answers your dev-related first three points, let me answer your last one.
Yes, automated tests for frontend workflow would be highly appreciated. Could you possibly open a new issue with test requirements in dashboard repo? That ways we can have a more in-depth discussion, with inputs from @danimair9 as well.
Create a develop branch and add a GitHub workflow that builds develop FE images for testing purposes like this:
Create alpha tags
https://github.com/oakestra/oakestra/blob/develop/.github/workflows/create-alpha-tags.yml
This creates an alpha tag from a push in develop triggering the new build
The text was updated successfully, but these errors were encountered: