Project

General

Profile

Actions

User story #2214

closed

Set an identifiable tag in message and meaningfull user for git archive commit

Added by François ARMAND about 12 years ago. Updated almost 12 years ago.

Status:
Released
Priority:
3
Category:
Web - Maintenance
Target version:
UX impact:
Suggestion strength:
User visibility:
Effort required:
Name check:
Fix check:
Regression:

Description

To let advanced users (and future developers) write scripts and code to retrieve archives, commit message for them must contains an identifiable part.

I propose:

  • #groups-archive for an archive commit for groups
  • #policy-library-archive for an archive of the policy library
  • #configuration-rules-archive for an archive of the configuration rules
  • #full-archive for archive of all of the three

With the same idea, the actor who started the archive should be set as the author of the commit.

Actions #1

Updated by François ARMAND about 12 years ago

  • Status changed from 2 to In progress
Actions #2

Updated by François ARMAND about 12 years ago

  • Subject changed from Set an identifiable git commit message for archive message. to Set an identifiable tag in message and meaningfull user for git archive commit
  • Description updated (diff)
Actions #3

Updated by François ARMAND about 12 years ago

Event better than simply an identifiable message, we should create a tag, like that:

  • archives/groups/iso-datetime for an archive commit for groups
  • archives/policy-library/iso-datetime for an archive of the policy library
  • archives/configuration-rules/iso-datetime for an archive of the configuration rules
  • archives/full/iso-datetime for archive of all of the three
Actions #4

Updated by François ARMAND about 12 years ago

The "actor as commiter" part will be done in a different ticket, see #2215

Actions #5

Updated by François ARMAND about 12 years ago

  • Status changed from In progress to Pending technical review
  • % Done changed from 0 to 100
Actions #6

Updated by Nicolas CHARLES about 12 years ago

  • Status changed from Pending technical review to 10

Based on my limited skill in JGit, this looks valid. Thank you Francois

Actions #7

Updated by Jonathan CLARKE almost 12 years ago

  • Status changed from 10 to Released
Actions

Also available in: Atom PDF