Hi folks. My team is considering moving onto grap...
# how-do-i
e
Hi folks. My team is considering moving onto graphite and we have an existing github action process we worried might conflict with graphite. A bot updates versions in code on every push to main. Will that disrupt the graphite merge queue?
p
(If applicable) To help us more clearly understand what you're trying to do, please provide additional details about: - Screenshots / debug logs / list of commands you've tried to run so far - Your workflow - Current state
Hey Eddie! I think you may be fine, but I'm double-checking with the team to confirm. I'll let you know once I learn more 🙏
e
thanks for looking into it! we're concerned with graphite merging several PRs quickly without giving the versioning job time to complete. is there a way to ensure a job runs between graphite merges?
p
I suspect you'll want to configure this at the GitHub level. If you can configure these jobs as required GitHub status checks, Graphite will respect those checks. You could also configure GitHub actions to trigger on
push
events to main, which would run after each merge.