SkyeYoung opened a new pull request, #12199:
URL: https://github.com/apache/apisix/pull/12199

   ### Description
   
   <!-- Please include a summary of the change and which issue is fixed. -->
   <!-- Please also include relevant motivation and context. -->
   
   Fix according to the records here: apache/infrastructure-asfyaml@6a03ced
   
   Because I received the following email while developing 
`apisix-dashboard`(I've also repaired it there 
https://github.com/apache/apisix-dashboard/pull/3026):
   
   ```
   An error occurred while processing the github feature in .asf.yaml:
   
   while parsing a mapping
     in "apisix-dashboard.git/.asf.yaml::github", line 20, column 1:
      
       ^ (line: 20)
   unexpected key not in schema 'notifications'
     in "apisix-dashboard.git/.asf.yaml::github", line 24, column 1:
         pullrequests: notifications@ap ...
       ^ (line: 24)
   
   ---
   With regards, ASF Infra.
   For further information, please see the .asf.yaml documentation at:
   https://github.com/apache/infrastructure-asfyaml/blob/main/README.md
   ```
   
   
   #### Which issue(s) this PR fixes:
   <!--
   *Automatically closes linked issue when PR is merged.
   Usage: `Fixes #<issue number>`, or `Fixes (paste link of issue)`.
   -->
   Fixes #
   
   ### Checklist
   
   - [x] I have explained the need for this PR and the problem it solves
   - [x] I have explained the changes or the new features added to this PR
   - [ ] I have added tests corresponding to this change
   - [ ] I have updated the documentation to reflect this change
   - [ ] I have verified that this change is backward compatible (If not, 
please discuss on the [APISIX mailing 
list](https://github.com/apache/apisix/tree/master#community) first)
   
   <!--
   
   Note
   
   1. Mark the PR as draft until it's ready to be reviewed.
   2. Always add/update tests for any changes unless you have a good reason.
   3. Always update the documentation to reflect the changes made in the PR.
   4. Make a new commit to resolve conversations instead of `push -f`.
   5. To resolve merge conflicts, merge master instead of rebasing.
   6. Use "request review" to notify the reviewer after making changes.
   7. Only a reviewer can mark a conversation as resolved.
   
   -->
   


-- 
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: notifications-unsubscr...@apisix.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Reply via email to