test

[akanshaaa19]

Summary by CodeRabbit

• Chores
  • Updated the release workflow to trigger on pull requests instead of pushes to the main branch.
  • Added automatic upload of merged documentation as an artifact with 30-day retention.

[coderabbitai]

📝 Walkthrough

Walkthrough

Modified the GitHub Actions workflow to trigger on pull requests instead of push events on the main branch, and added a new step to upload the merged documentation file as a workflow artifact with a 30-day retention period.

Changes

Cohort / File(s)	Summary
Workflow Configuration .github/workflows/export_and_update.yml	Changed trigger event from push to pull_request on main branch; added final artifact upload step for merged_documentation.md with 30-day retention using actions/upload-artifact@v4.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🐰 A workflow hops from push to pull,
Now checking PRs when change is full,
Documentation bundled with care,
Artifacts saved in the CI air! 📦✨

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title check	❓ Inconclusive	The title 'test' is vague and generic, failing to describe any meaningful aspect of the changeset which modifies workflow triggers and adds artifact upload functionality.	Use a descriptive title that summarizes the actual changes, such as 'Update workflow to trigger on pull requests and add documentation artifact upload'.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch test

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[github-actions]

🚀 Deployed on https://deploy-preview-581--glific-docs.netlify.app

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In @.github/workflows/export_and_update.yml:
- Around line 4-5: The workflow currently triggers on pull_request for main
which allows unmerged PRs to run destructive Step 5 (vector-store
delete/replace); change the trigger or add a guard so only pushes to main can
perform mutations: keep pull_request for building/artifact steps but wrap the
destructive job/step (referenced as Step 5 / the vector-store update step) with
a condition such as if: github.event_name == 'push' && github.ref ==
'refs/heads/main' or move the vector-store update into a separate workflow
triggered only on push to main so PRs (and forked PRs without secrets) cannot
mutate production data.

---

ℹ️ Review info

Configuration used: defaults

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between d478d16 and 8ececb9.

📒 Files selected for processing (1)

• .github/workflows/export_and_update.yml

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

Restrict production vector-store mutations to post-merge events

Line 4 now runs this workflow on every PR update, but Step 5 performs destructive external operations (delete + replace in the vector store). That allows unmerged PR code to mutate production data and can also fail on fork PRs due to missing secrets.

🔧 Suggested fix (keep artifact on PR, run vector-store update only on push to main)

 on:
   pull_request:
     branches: [main]
+  push:
+    branches: [main]
@@
       # Step 5: Upload to Vector Store
       - name: Upload to Vector Store
+        if: github.event_name == 'push'
         env:
           OPENAI_API_KEY: ${{ secrets.OPENAI_API_KEY }}
           VECTOR_STORE_ID: ${{ secrets.VECTOR_STORE_ID }}

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In @.github/workflows/export_and_update.yml around lines 4 - 5, The workflow
currently triggers on pull_request for main which allows unmerged PRs to run
destructive Step 5 (vector-store delete/replace); change the trigger or add a
guard so only pushes to main can perform mutations: keep pull_request for
building/artifact steps but wrap the destructive job/step (referenced as Step 5
/ the vector-store update step) with a condition such as if: github.event_name
== 'push' && github.ref == 'refs/heads/main' or move the vector-store update
into a separate workflow triggered only on push to main so PRs (and forked PRs
without secrets) cannot mutate production data.