Azure
Removal of deprecated workflows?
Describe the bug when forking repo, some deprecated workflows are still present and creating unnecessary errors. aka
- .github/workflows/convertKqlFuncYamlToArmTemplate.yaml
- .github/workflows/runAsimTesters.yaml resulting in
Error: .github#L1
No event triggers defined in `on`
See for example https://github.com/juju4/Azure-Sentinel/actions
Above file are empty and replaced by https://github.com/Azure/Azure-Sentinel/blob/master/.github/workflows/convertKqlFunctionYamlToArmTemplate.yaml https://github.com/Azure/Azure-Sentinel/blob/master/.github/workflows/runAsimSchemaAndDataTesters.yaml since 2 months it seems.
To Reproduce Steps to reproduce the behavior:
- Fork repo
- Run actions
Expected behavior Get same actions state than parent
Thank you for submitting an Issue to the Azure Sentinel GitHub repo! You should expect an initial response to your Issue from the team within 5 business days. Note that this response may be delayed during holiday periods. For urgent, production-affecting issues please raise a support ticket via the Azure Portal.
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
Thank you for submitting an Issue to the Azure Sentinel GitHub repo! You should expect an initial response to your Issue from the team within 5 business days. Note that this response may be delayed during holiday periods. For urgent, production-affecting issues please raise a support ticket via the Azure Portal.
Thank you for submitting an Issue to the Azure Sentinel GitHub repo! You should expect an initial response to your Issue from the team within 5 business days. Note that this response may be delayed during holiday periods. For urgent, production-affecting issues please raise a support ticket via the Azure Portal.
Thank you for submitting an Issue to the Azure Sentinel GitHub repo! You should expect an initial response to your Issue from the team within 5 business days. Note that this response may be delayed during holiday periods. For urgent, production-affecting issues please raise a support ticket via the Azure Portal.
Thank you for submitting an Issue to the Azure Sentinel GitHub repo! You should expect an initial response to your Issue from the team within 5 business days. Note that this response may be delayed during holiday periods. For urgent, production-affecting issues please raise a support ticket via the Azure Portal.
Thank you for submitting an Issue to the Azure Sentinel GitHub repo! You should expect an initial response to your Issue from the team within 5 business days. Note that this response may be delayed during holiday periods. For urgent, production-affecting issues please raise a support ticket via the Azure Portal.
Hi @juju4, Gentle Reminder: We are awaiting for your response on this issue. If you still need to keep this issue active please respond on it in the next 2 days. If we don't receive response, we will be close this issue.
This issue won't be fixed without any change.
That's polluting any fork of the repo. Example with mine: https://github.com/juju4/Azure-Sentinel/actions as shared previously
Hi @juju4 thanks for confirming we will work with the team on this and update you shortly.
Hi @juju4, we are waiting for response from the respective team, we will provide you an update.
Thank you for submitting an Issue to the Azure Sentinel GitHub repo! You should expect an initial response to your Issue from the team within 5 business days. Note that this response may be delayed during holiday periods. For urgent, production-affecting issues please raise a support ticket via the Azure Portal.