Pre-publishing check and auto-commit

When publishing a project under source control, no check is in place whether all changes have been committed on all files. Also, publishing does not automatically commit the Json-file, meaning that there is a possibility of a disconnect between packages and the associated files. I would like to request the following features:

  • before publishing, check if all files have no local-only changes;
  • after publishing, automatically commit the Json-file with an informative message, e.g publish v1.0.123.4567

It’s same situation if you are working on a Visual Studio Project: Before Release, make sure you have updated the changes with your Repository, Resolve Conflicts or Merges. Additionally Robot would have to know Repo Credentials, Type of Source Control System…
Source Control Management is a Developer Responsibility I guess :wink:

1 Like