Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
    • Help
    • Submit feedback
  • Sign in
Trial
Trial
  • Project
    • Project
    • Details
    • Activity
    • Releases
    • Cycle Analytics
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Charts
  • Issues 7
    • Issues 7
    • List
    • Board
    • Labels
    • Milestones
  • Merge Requests 1
    • Merge Requests 1
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Charts
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Charts
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • TC LI - Lawful Interception
  • TrialTrial
  • Issues
  • #4

Closed
Open
Opened Jun 15, 2020 by canterburym@canterburym
  • Report abuse
  • New issue
Report abuse New issue

Can standards tags be applied to commits only for the standard they tag?

Given the current merge process (CRs are all agreed and merged back in to a single meeting branch), is there a sane way to add the standards tags such that they actually label a commit which represents the changes to that standard (as opposed to the output of the meeting)?

The preload script that populated the repo is able to do this because it doesn't use the branching strategy; each new version is a single commit which can then be tagged.

Edited Jun 15, 2020 by canterburym
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
No due date
0
Labels
None
Assign labels
  • View project labels
Reference: li/trial#4