taojintianxia commented on issue #26521:
URL: 
https://github.com/apache/shardingsphere/issues/26521#issuecomment-1752283484

   > Hi @taojintianxia
   > 
   > It seems like the nightly-build workflow last execution 
([link](https://github.com/apache/shardingsphere/actions/runs/6448611936)) 
failed because of the github action `tunaitis/contributor-map@v1` is not 
allowed to be used in this repo
   > 
   > ```
   > [Error: 
.github#L1](https://github.com/apache/shardingsphere/commit/1e2fe35851f21809c34027e4fba2d5772a7fb006#annotation_14737341013)
   > tunaitis/contributor-map@v1 is not allowed to be used in 
apache/shardingsphere. Actions in this workflow must be: within a repository 
owned by apache, created by GitHub, verified in the GitHub Marketplace, or 
matching the following: 
*/*@[a-f0-9][a-f0-9][a-f0-9][a-f0-9][a-f0-9][a-f0-9][a-f0-9]+, 
AdoptOpenJDK/install-jdk@*, 
JamesIves/github-pages-deploy-action@5dc1d5a192aeb5ab5b7d5a77b7d36aea4a7f5c92, 
TobKed/label-when-approved-action@*, actions-cool/issues-helper@*, 
actions-rs/*, al-cheb/configure-pagefile-action@*, 
amannn/action-semantic-pull-request@*, apache/*, 
burrunan/gradle-cache-action@*, bytedeco/javacpp-presets/.github/actions/*, 
chromaui/action@*, codecov/codecov-action@*, conda-incubator/setup-miniconda@*, 
container-tools/kind-action@*, container-tools/microshift-action@*, 
dawidd6/action-download-artifact@*, delaguardo/setup-graalvm@*, 
docker://jekyll/jekyll:*, docker://pandoc/core:2.9, 
eps1lon/actions-label-merge-conflict@*, 
gaurav-nelson/github-action-markdown-link-c
 heck...
   > ```
   
   yes, it's not working in this repository. let's revert the change, remove 
the action and svg link from markdown file.
   let's test it in forked repository and then commit the PR.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to