Skip to content

Conversation

@NabilMx99
Copy link

@NabilMx99 NabilMx99 commented Jan 19, 2026

This pull request introduces a new feature to the verifications branch that adds tagging verification functionality for
the tag-it exercise. The feature includes the following changes:

New Exercise tag-it

  • A new exercise, tag-it, has been added to the repository. This exercise is designed to help users practice creating and verifying Git tags. See New Exercise: tag-it #67

  • The exercise requires users to create two commits and associate them with specific tags (v0.1.0 and v0.2.0).

Verification Logic

  • The exercise verification logic has been implemented in the TagIt.php file.

  • The verification ensures:

    • Two commits are present in the branch.
    • The correct file App/src/Program.cs is modified in both commits.
    • Each commit has exactly one tag associated with it.
    • The tags v0.1.0 & v0.2.0 are correctly associated with the respective commits.

Updates to start.sh script

  • The start.sh script initializes the exercise environment by creating the first commit and tag v0.1.0 and setting up the environment for the user to create the second commit and tag v0.2.0. See New Exercise: tag-it #67

Other changes

Rec1.mp4

⚠️ Tagging Verification Issue

While testing the tag-it exercise, I encountered an issue where the git verify command fails with the following error:

Rec2.mp4
screenshot

After thorough investigation, I identified that the root cause of this issue is that the tag-it branch exists in my fork but does not exist in the original repository. The server-side hook in the original repository validates the branch name against a predefined list of valid exercises. Since the tag-it branch is not present in the original repository, the hook rejects the push and does not process the tags.

I kindly request that you review this pull request, create a branch named tag-it, and merge the changes into it. This will allow the exercise to be recognized as a valid exercise by the server-side hook, resolving the verification issue.

@NabilMx99 NabilMx99 marked this pull request as ready for review January 19, 2026 15:02
@NabilMx99
Copy link
Author

NabilMx99 commented Jan 24, 2026

Hi @fracz. Just wanted to kindly follow up on this pull request. Please let me know if there's anything I can clarify or improve. Thank you for your time and consideration🙏🏻

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant