馃摎 Archivist: Clarify CI trigger conditions for prerelease builds - #486
Conversation
Co-authored-by: 2fst4u <15257926+2fst4u@users.noreply.github.com>
|
馃憢 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 馃憖 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
馃摎 Archivist: Clarify CI trigger conditions for prerelease builds
馃挕 Problem:
AGENTS.mdincorrectly claimed that automatic prerelease dev builds were triggered by pushes to "any branch", including "direct main pushes". However,.github/workflows/build.ymlcontains abranches-ignore: - mainclause and apaths-ignoreblock for markdown and workflow files, meaning the documentation was completely false regarding themainbranch.馃幆 Fix:
mainbranch, markdown files, and workflow files are ignored.mainfrom the dev branch tag example text.馃И Verification:
.github/workflows/build.ymltriggers manually usingcat.AGENTS.mdand.jules/archivist.mdwithprettier.make testto ensure no infrastructure tests (liketest_release_config.py) were broken.馃攷 Scope:
This PR contains ONLY documentation changes to
AGENTS.mdand a new critical learning entry in.jules/archivist.md.PR created automatically by Jules for task 5190970421697098366 started by @2fst4u