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
Copy file name to clipboardExpand all lines: README.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -48,8 +48,8 @@ If you are looking for a simple challenge configuration that you can replicate t
48
48
49
49
5. Create a branch with name `challenge` in the forked repository from the `master` branch.
50
50
<spanstyle="color:purple">Note: Only changes in `challenge` branch will be synchronized with challenge on EvalAI.</span>
51
-
You may maintain multiple versions by using additional branches whose names start with`challenge-` (e.g. `challenge-2024`, `challenge-v2`).
52
-
<spanstyle="color:purple">Note: The CI pipeline only runs for branches that match the pattern `challenge` or `challenge-*`. Any other branch name will be ignored.</span>
51
+
You may maintain multiple versions by using additional branches that follow the pattern`challenge-<year>-<version>` (e.g. `challenge-2024-v1`, `challenge-2024-beta`, `challenge-2025-final`).
52
+
<spanstyle="color:purple">Note: The CI pipeline only runs for branches that match the pattern `challenge` or `challenge-YYYY-version`. Any other branch name will be ignored.</span>
53
53
54
54
If you trigger the processing script manually and do **not** pass a branch argument, it will assume the branch name is `challenge` by default.
print("Error: Branch name must follow the pattern 'challenge' or 'challenge-<year>-<version>' (e.g., 'challenge', 'challenge-2024-v1', 'challenge-2024-beta').")
0 commit comments