Committing Order Status Picklist Field and StandardValueSet Returns a No Changes Message

When you commit the Status field in the Order object or the OrderStatus standard value set, you may receive the error message below:

"The latest commit contains No Changes. This happens when the selected components are equal to their corresponding files in Git. To remove this warning delete the No Changes commit from the User Story Commits related list."

This basically means that you are not making any changes in the feature branch created out of master. This happens because, according to Salesforce’s official documentation, some standard value set names and standard picklist fields are not supported by the MetaData API and can't be retrieved or deployed, therefore you are not making any changes when committing. You can check the list of supported standard picklist field in Salesforce’s article StandardValueSet Names and Standard Picklist Fields.

Please, bear in mind that if you commit this standard value set along with other components, you will not get a ‘No Changes’ error and the commit will be successful. However, you will receive the following error if you try to deploy it:

"[ OrderStatus] An object 'OrderStatus' of type StandardValueSet was named in package.xml, but was not found in zipped directory" .

How did we do?