diff --git a/path/to/.github/workflows/RunIssueSentinel.yml b/path/to/.github/workflows/RunIssueSentinel.yml new file mode 100644 index 00000000..ae5044c1 --- /dev/null +++ b/path/to/.github/workflows/RunIssueSentinel.yml @@ -0,0 +1,59 @@ +# Define a workflow to run the issue sentinel +name: Run issue sentinel + +on: + issues: + types: [opened, edited, closed] + +jobs: + Issue: + permissions: + issues: write + runs-on: ubuntu-latest + steps: + - name: Run Issue Sentinel + uses: Azure/issue-sentinel@v1 + with: + # Define a function to analyze an issue + analyze_issue: | + import os + import requests + import json + import traceback + + def analyze_issue(issue): + try: + # Get the issue title and description + title = issue['title'] + description = issue['description'] + + # Check if the issue is related to silent breaking changes or unverifiable remote code + if 'silent breaking change' in title.lower() or 'unverifiable remote code' in description.lower(): + return True + else: + return False + except Exception as e: + print(f"Error analyzing issue: {e}") + return None + + # Define a function to process regression feedback + process_regression_feedback: | + import os + import requests + import json + import traceback + + def process_regression_feedback(feedback): + try: + # Get the feedback title and description + title = feedback['title'] + description = feedback['description'] + + # Check if the feedback is related to silent breaking changes or unverifiable remote code + if 'silent breaking change' in title.lower() or 'unverifiable remote code' in description.lower(): + return True + else: + return False + except Exception as e: + print(f"Error processing feedback: {e}") + return None \ No newline at end of file diff --git a/path/to/README.md b/path/to/README.md new file mode 100644 index 00000000..02b2b9ff --- /dev/null +++ b/path/to/README.md @@ -0,0 +1,15 @@ +# Office JavaScript APIs for Office Add-ins + +Use Office.js and the Office Add-ins platform to build solutions that extend Office applications and interact with content in Office documents and in Outlook mail messages and calendar items. With Office Add-ins, you can use familiar web technologies such as HTML, CSS, and JavaScript to build solutions that can run in Office on the web, Windows, Mac, and mobile. You'll find walkthroughs, samples, and more information in the official [Office Add-ins documentation](https://learn.microsoft.com/office/dev/add-ins/). + +## This repository + +This GitHub repository is primarily used to report issues found in the Office JavaScript APIs. The npm package associated with this repository is no longer officially supported. Your add-in should get the JavaScript library from the Office content delivery network (CDN), as described in the section [Reference Office.js from the CDN](#reference-officejs-from-the-cdn). This ensures that essential product updates are served quickly to Office Add-ins. + +## Report issues + +If you believe you've found an issue (bug) with the Office JavaScript APIs, please visit the [issues tab](https://github.com/OfficeDev/office-js/issues) of this repo. If your issue is already reported, consider adding additional context or reproduction steps. Otherwise, select **New issue**, choose **Bug report**, and provide as much detail as possible. A member of our team will respond within 1-2 business days. + +## Reference Office.js from the CDN + +The Office CDN is the official supported source for Office Add-ins. Reference the Office.js library in the CDN by adding the following `