Fulfilment-Automater/sn
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

[Historical Commit 1] Fulfilment Automater

Browse Source 
Description: This application helps automate fulfilment processes through data-driven configurations.
Update Set was installed on 2023-01-13 13:46:57
Update Set was completed by admin admin@example.com
This commit is contained in:
admin
2023-01-13 13:46:52 -08:00
parent 039c6d58b2
commit 46f1e61f2c
32 changed files with 1334 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
c04afa629713111093a8337e6253af6d/README.md Normal file
View File

@ -0,0 +1,11 @@
# Update Set Commit History
This commit, and any commits following that contain the prefix [Historical Commit], were generated because 'Retain update set history as commits' was selected when this application was linked to Source Control.
1. For every completed update set containing updates relevant to this application, commits have been generated automatically by the system.
2. Updates are separated into multiple commits:
* if there are updates for a file that are out of order between different update sets
* if an update set contains multiple update records for a single file
The commits for an update set have been split into multiple commits ([Historical Commit 1], [Historical Commit 2]...) to represent each update. This is done so that each file has an in order history of updates.
3. The most recent commit is the current state of your application in its entirety.
WARNING: Any commit prefixed by [Historical Commit] is generated solely to display its history. Do not attempt to check out these commits in the development process as they do not necessarily represent a stable snapshot of the application.
See additional documentation: https://docs.servicenow.com/csh?topicname=migrate-update-set-history.html&version=latest