Given a main
branch used in a trunk-based development strategy, here is how semantic release can fit in:
%%{init: {
'logLevel': 'debug',
'theme': 'default' ,
'themeVariables': {
'git0': '#777',
with | |
-- Establish some test cases with expected outputs. | |
-- Note that this is the extent of the testing. | |
-- No claims are made to complete correctness for the full range of numbers - only for the following tests is it guaranteed. | |
test_cases as ( | |
select | |
num, | |
description, | |
expected_output |
# VSCode: use the Metals BSP plugin to integrate - https://marketplace.visualstudio.com/items?itemName=scalameta.metals | |
# IntelliJ: use the built-in support with scalafmt - https://www.jetbrains.com/help/idea/work-with-scala-formatter.html | |
# Required: | |
version = "3.5.3" | |
runner.dialect = scala213 | |
# Optional: | |
style = defaultWithAlign # Align pattern matching statements, variable decls, function defs, adjacent symbols, etc... | |
maxColumn = 120 # Monitors of the 20th century rejoice |