feat(incident): activity tab

.dockerignore

@@ -0,0 +1,8 @@
+docs/*
+keep-ui/node_modules
+keep-ui/.next/*
+keep-ui/.env.local
+.venv/
+.vercel/
+.vscode/
+.github/

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,27 @@
+---
+name: Bug report
+about: Create a report to help us improve
+title: "[🐛 Bug]: "
+labels: ""
+assignees: ""
+---
+
+**Describe the bug**
+A clear and concise description of what the bug is.
+
+**To Reproduce**
+Steps to reproduce the behavior:
+
+1. Go to '...'
+2. Click on '....'
+3. Scroll down to '....'
+4. See error
+
+**Expected behavior**
+A clear and concise description of what you expected to happen.
+
+**Screenshots**
+If applicable, add screenshots to help explain your problem.
+
+**Additional context**
+Add any other context about the problem here.

.github/ISSUE_TEMPLATE/documentation.md

@@ -0,0 +1,10 @@
+---
+name: Documentation issue
+about: Any issue related with Keep's documentation
+title: "[📃 Docs]: "
+labels: "Documentation"
+assignees: ""
+---
+
+**Describe the documentation change**
+Add any context about the documentation change you aim to do.

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,19 @@
+---
+name: Feature request
+about: Suggest an idea for this project
+title: "[➕ Feature]: "
+labels: ""
+assignees: ""
+---
+
+**Is your feature request related to a problem? Please describe.**
+A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
+
+**Describe the solution you'd like**
+A clear and concise description of what you want to happen.
+
+**Describe alternatives you've considered**
+A clear and concise description of any alternative solutions or features you've considered.
+
+**Additional context**
+Add any other context or screenshots about the feature request here.

.github/ISSUE_TEMPLATE/new_provider_request.md

@@ -0,0 +1,19 @@
+---
+name: New provider request
+about: Suggest a new provider for keep
+title: "[🔌 Provider]: "
+labels: "Provider"
+assignees: ""
+---
+
+**Describe the provider you want to add**
+Add any context about the tool and the kind of data you would want to pull/push from the provider.
+
+**Describe your use case**
+Does this integration will help you to use Keep?
+
+**Are you already using Keep?**
+Yes/No
+
+**Additional context**
+Add any other context or screenshots about the provider request here.

.github/ISSUE_TEMPLATE/use_case.md

@@ -0,0 +1,11 @@
+---
+name: Use case
+about: Tell us how you use Keep and we will add it to the docs.
+title: ''
+labels: ''
+assignees: ''
+
+---
+
+**What do you use Keep for?**
+A clear and concise description of what you do with Keep.

.github/workflows/developer_onboarding_notification.yml

@@ -0,0 +1,116 @@
+name: Celebrating Contributions
+
+on:
+  pull_request_target:
+    types: [closed]
+
+permissions:
+  pull-requests: write
+
+jobs:
+  comment_on_merged_pull_request:
+    if: github.event.pull_request.merged == true
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout Repository
+        uses: actions/checkout@v4
+
+      - name: Set Environment Variables
+        env:
+          AUTHOR: ${{ github.event.pull_request.user.login }}
+          REPO: ${{ github.event.repository.name }}
+          OWNER: ${{ github.event.repository.owner.login }}
+        run: |
+          echo "AUTHOR=${AUTHOR}" >> $GITHUB_ENV
+          echo "REPO=${REPO}" >> $GITHUB_ENV
+          echo "OWNER=${OWNER}" >> $GITHUB_ENV
+
+      - name: Count Merged Pull Requests
+        id: count_merged_pull_requests
+        uses: actions/github-script@v6
+        with:
+          github-token: ${{ secrets.GITHUB_TOKEN }}
+          script: |
+            try {
+              const author = process.env.AUTHOR;
+              const repo = process.env.REPO;
+              const owner = process.env.OWNER;
+              const { data } = await github.rest.search.issuesAndPullRequests({
+                q: `repo:${owner}/${repo} type:pr state:closed author:${author}`
+              });
+              const prCount = data.items.filter(pr => pr.pull_request.merged_at).length;
+              core.exportVariable('PR_COUNT', prCount);
+            } catch (error) {
+              core.setFailed(`Error counting merged pull requests: ${error.message}`);
+            }
+
+      - name: Comment on the Merged Pull Request
+        uses: actions/github-script@v6
+        with:
+          github-token: ${{ secrets.GITHUB_TOKEN }}
+          script: |
+            try {
+              const prCount = parseInt(process.env.PR_COUNT);
+              const author = process.env.AUTHOR;
+              const mention = 'talboren'; 
+              const prNumber = context.payload.pull_request.number;
+              const repo = process.env.REPO;
+
+              function getRandomEmoji() {
+                const emojis = ['🎉', '🚀', '💪', '🌟', '🏆', '🎊', '🔥', '👏', '🌈', '🚂'];
+                return emojis[Math.floor(Math.random() * emojis.length)];
+              }
+
+              function getMessage(count) {
+                const emoji = getRandomEmoji();
+                switch(count) {
+                  case 1:
+                    return `${emoji} **Fantastic work @${author}!** Your very first PR to ${repo} has been merged! 🎉🥳\n\n` +
+                           `You've just taken your first step into open-source, and we couldn't be happier to have you onboard. 🙌\n` +
+                           `If you're feeling adventurous, why not dive into another issue and keep contributing? The community would love to see more from you! 🚀\n\n` +
+                           `For any support, feel free to reach out to the developer onboarding lead: @${mention}. Happy coding! 👩‍💻👨‍💻`;
+                  case 2:
+                    return `${emoji} **Well done @${author}!** Two PRs merged already! 🎉🥳\n\n` +
+                           `With your second PR, you're on a roll, and your contributions are already making a difference. 🌟\n` +
+                           `Looking forward to seeing even more contributions from you. The developer onboarding lead: @${mention} is here if you need any help! Keep up the great work! 🚀`;
+                  case 3:
+                    return `${emoji} **You're on fire, @${author}!** Three PRs merged and counting! 🔥🎉\n\n` +
+                           `Your consistent contributions are truly impressive. You're becoming a valued member of our community! 💖\n` +
+                           `Have you considered taking on some more challenging issues? We'd love to see what you can do! 💪\n\n` +
+                           `Remember, @${mention} is always here to support you. Keep blazing that trail! 🚀`;
+                  case 5:
+                    return `${emoji} **High five, @${author}!** You've hit the incredible milestone of 5 merged PRs! 🖐️✨\n\n` +
+                           `Your dedication to ${repo} is outstanding. You're not just contributing code; you're shaping the future of this project! 🌠\n` +
+                           `We'd love to hear your thoughts on the project. Any ideas for new features or improvements? 🤔\n\n` +
+                           `@${mention} and the whole team applaud your efforts. You're a superstar! 🌟`;
+                  case 10:
+                    return `${emoji} **Double digits, @${author}!** 10 merged PRs is a massive achievement! 🏆🎊\n\n` +
+                           `Your impact on ${repo} is undeniable. You've become a pillar of our community! 🏛️\n` +
+                           `We'd be thrilled to have you take on a mentorship role for newer contributors. Interested? 🧑‍🏫\n\n` +
+                           `@${mention} and everyone here are in awe of your contributions. You're an open source hero! 🦸‍♀️🦸‍♂️`;
+                  default:
+                    if (count > 10) {
+                      return `${emoji} **Incredible, @${author}!** You've merged your ${count}th PR! 🎯🎊\n\n` +
+                             `Your ongoing commitment to ${repo} is truly remarkable. You're a driving force in our community! 🚀\n` +
+                             `Your contributions are helping to shape the future of this project. What exciting features or improvements do you envision next? 🔮\n\n` +
+                             `@${mention} and the entire team are grateful for your dedication. You're an inspiration to us all! 💫`;
+                    } else {
+                      return `${emoji} **Great job, @${author}!** You've merged your ${count}th PR! 🎊\n\n` +
+                             `Your contributions to ${repo} are making a real difference. Keep up the fantastic work! 💪\n` +
+                             `Remember, every PR counts and helps improve the project. What will you tackle next? 🤔\n\n` +
+                             `@${mention} is here if you need any guidance. Onward and upward! 🚀`;
+                    }
+                }
+              }
+
+              const message = getMessage(prCount);
+
+              await github.rest.issues.createComment({
+                owner: process.env.OWNER,
+                repo: process.env.REPO,
+                issue_number: prNumber,
+                body: message
+              });
+            } catch (error) {
+              core.setFailed(`Error creating comment: ${error.message}`);
+            }

.github/workflows/lint-pr.yml

@@ -0,0 +1,56 @@
+name: "Lint PR"
+
+on:
+  pull_request_target:
+    types:
+      - opened
+      - edited
+      - synchronize
+      - reopened
+
+jobs:
+  main:
+    name: Validate PR title
+    runs-on: ubuntu-latest
+    steps:
+      - name: lint_pr_title
+        id: lint_pr_title
+        uses: amannn/[email protected]
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+      - uses: marocchino/sticky-pull-request-comment@v2
+        # When the previous steps fails, the workflow would stop. By adding this
+        # condition you can continue the execution with the populated error message.
+        if: always() && (steps.lint_pr_title.outputs.error_message != null)
+        with:
+          header: pr-title-lint-error
+          message: |
+            Hey there and thank you for opening this pull request! 👋🏼
+
+            We require pull request titles to follow the [Conventional Commits specification](https://www.conventionalcommits.org/en/v1.0.0/) and it looks like your proposed title needs to be adjusted.
+
+            Details:
+
+            ```
+            ${{ steps.lint_pr_title.outputs.error_message }}
+            ```
+      # Delete a previous comment when the issue has been resolved
+      - if: ${{ steps.lint_pr_title.outputs.error_message == null }}
+        uses: marocchino/sticky-pull-request-comment@v2
+        with:
+          header: pr-title-lint-error
+          delete: true
+  links:
+    runs-on: ubuntu-latest
+    name: Validate PR to Issue link
+    permissions:
+      issues: read
+      pull-requests: write
+    steps:
+      - uses: nearform-actions/github-action-check-linked-issues@v1
+        id: check-linked-issues
+        with:
+          exclude-branches: "release/**, dependabot/**"
+      # OPTIONAL: Use the output from the `check-linked-issues` step
+      - name: Get the output
+        run: echo "How many linked issues? ${{ steps.check-linked-issues.outputs.linked_issues_count }}"

.github/workflows/release.yml

@@ -0,0 +1,58 @@
+name: Keep Release
+
+on:
+  workflow_dispatch:
+
+jobs:
+  release:
+    runs-on: ubuntu-latest
+    concurrency: release
+    permissions:
+      id-token: write
+      contents: write
+      pull-requests: write
+
+    steps:
+      - uses: actions/checkout@v3
+        with:
+          fetch-depth: 0
+          persist-credentials: false
+          ref: main
+
+      - name: Release Keep
+        id: release-step
+        uses: python-semantic-release/[email protected]
+        with:
+          git_committer_name: Keep Release Bot
+          git_committer_email: [email protected]
+          github_token: ${{ secrets.GITHUB_TOKEN }}
+          push: false
+          tag: true
+          commit: true
+
+      - name: Open PR for release branch
+        id: pr-step
+        uses: peter-evans/[email protected]
+        with:
+          committer: Keep Release Bot <[email protected]>
+          title: "Release - ${{ steps.release-step.outputs.version }}"
+          branch: release/${{ steps.release-step.outputs.version }}
+          body: "This PR contains the latest release changes."
+          draft: false
+          base: main
+
+      - uses: peter-evans/enable-pull-request-automerge@v3
+        with:
+          token: ${{ secrets.GITHUB_TOKEN }}
+          pull-request-number: ${{ steps.pr-step.outputs.pull-request-number }}
+
+      - name: Create release
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          tag: "v${{ steps.release-step.outputs.version }}"
+        run: |
+          gh release create "$tag" \
+              --repo="$GITHUB_REPOSITORY" \
+              --title="v${{ steps.release-step.outputs.version }}" \
+              --target="release/${{ steps.release-step.outputs.version }}" \
+              --generate-notes

.github/workflows/sync-keep-workflows.yml

@@ -0,0 +1,35 @@
+# A workflow that sync Keep workflows from a directory
+name: "Sync Keep Workflows"
+
+on:
+    workflow_dispatch:
+        inputs:
+            keep_api_key:
+              description: 'Keep API Key'
+              required: false
+            keep_api_url:
+              description: 'Keep API URL'
+              required: false
+              default: 'https://api.keephq.dev'
+    # push:
+    #     paths:
+    #       - 'examples/workflows/**'
+
+jobs:
+    sync-workflows:
+        name: Sync workflows to Keep
+        runs-on: ubuntu-latest
+        # Use the Keep CLI image
+        container:
+            image: us-central1-docker.pkg.dev/keephq/keep/keep-cli:latest
+        env:
+            KEEP_API_KEY: ${{ secrets.KEEP_API_KEY || github.event.inputs.keep_api_key }}
+            KEEP_API_URL: ${{ secrets.KEEP_API_URL || github.event.inputs.keep_api_url }}
+
+        steps:
+        - name: Check out the repo
+          uses: actions/checkout@v2
+
+        - name: Run Keep CLI
+          run: |
+            keep workflow apply -f examples/workflows