You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To prevent cases when the repository already has workflow files and to not override it accidently add check to gh-workflow that will verify first that the file is autogenerated and if not throw an Error.
The text was updated successfully, but these errors were encountered:
One way to identify that the file isn't generated by this tool is to see if the file starts with the initial block comment. That being said, when the file is generated, git will show a diff automatically and the user has the option to commit or not. What is the purpose of providing such low-level control over when to update the file?
One way to identify that the file isn't generated by this tool is to see if the file starts with the initial block comment. That being said, when the file is generated, git will show a diff automatically and the user has the option to commit or not. What is the purpose of providing such low-level control over when to update the file?
I though about case when the git is not yet initialized but there are some files already
To prevent cases when the repository already has workflow files and to not override it accidently add check to gh-workflow that will verify first that the file is autogenerated and if not throw an Error.
The text was updated successfully, but these errors were encountered: