-
Notifications
You must be signed in to change notification settings - Fork 60
Description
Describe the bug
The problem is that the action cannot load the configuration file from any directory outside of .github/workflows. Consequently, when the configuration file is placed within the 'workflows' directory, it triggers an error within GitHub actions due to a deviation from the expected workflow syntax.
No event triggers defined in "on"
To Reproduce
- Create a 'slack.yml' configuration file and locate it within the
.github/configdirectory. - Attempt to utilize the configuration file with the associated action.
Expected behavior
Ideally, users should have the flexibility to position the configuration file outside of the 'workflows' directory without encountering any issues.
Screenshots
In the following screenshots, you can observe the contrast between placing the configuration file in directories other than .github/workflows and adhering to the 'workflows' directory:
By putting the config file in any directory other than the .github/workflows, the action can not read config template!
# Step 14: Post breaking changes to a Slack channel
- name: Post breaking changes to a Slack channel
env:
SLACK_WEBHOOK_URL: ${{ secrets.SLACK_WEBHOOK_URL }}
uses: act10ns/slack@v1
with:
status: complete
channel: "#sci-design-system-breaking-changes"
config: .github/config/slack.yml
if: contains(toJson(github.event.commits.*.message), 'BREAKING CHANGE')
The message is constructed based on the template by putting the config file in the .github/workflows directory.
# Step 14: Post breaking changes to a Slack channel
- name: Post breaking changes to a Slack channel
env:
SLACK_WEBHOOK_URL: ${{ secrets.SLACK_WEBHOOK_URL }}
uses: act10ns/slack@v1
with:
status: complete
channel: "#sci-design-system-breaking-changes"
config: .github/workflows/slack.yml
if: contains(toJson(github.event.commits.*.message), 'BREAKING CHANGE')
Desktop (please complete the following information):
- OS: macOS Ventura 13.5.1
- Browser: Chrome
- Version: 116.0.5845.110 (Official Build) (arm64)
I appreciate your attention to this matter and kindly request assistance in resolving this issue to enhance the functionality and usability of the package.