Josh Soref —
This is me... There's nothing remotely exciting about the changes. Of late, when I file "issues" before making PRs like this, people tend to use AIs to write PRs to fix my issues...
#general
Hey @user; that gate is repo-wide right now, prolly not specific to you (@user is hitting the same wall above). For a fix that's already scoped against #3511 & addresses iskhakov's #3726 feedback, your fork and a Slack note (like the one you just posted) pointing to the diff is probably the right path under the current posture. Worth a careful read of [contributing.md](https://github.com/archestra-ai/archestra/blob/main/docs/pages/contributing.md) before posting anything substantive ... the "Contribute Responsibly" section is actively enforced. Short/specific should probably land better than long/structured, as the latter gets read as slop regardless of your effort in the matter. I'm a friendly community member without any skin in the game, but I'm happy to welcome you, and I genuinely wish you good luck! (FWIW @user same spam-filtering gate affecting you too it seems.)
👍1
1 reply
Hey beautiful people, I'm Awais, looking forward to making a contribution. Just got done with setting up dev environment
This is me... There's nothing remotely exciting about the changes. Of late, when I file "issues" before making PRs like this, people tend to use AIs to write PRs to fix my issues...
It's kinda unfortunate that
https://github.com/archestra-ai/archestra/blob/9c146cac00ace48500069723454205fe1526b3be/docs/pages/contributing.md?plain=1#L13 relies on a different layout than the one in git, it means that the image is broken when browsing the file https://github.com/archestra-ai/archestra/blob/main/docs/pages/contributing.md
Read-only live mirror of Archestra.AI Slack
👋Join the discussion withAI enthusiasts!This is me... There's nothing remotely exciting about the changes. Of late, when I file "issues" before making PRs like this, people tend to use AIs to write PRs to fix my issues...
15 replies
For some repositories, I'd make annotations explaining why I made changes, but this repository seems to want as little text as possible, so I'm not going to comment on it in the PR unless people have questions/requests.
Note that I did correct items in the changelog -- I understand they're copied from pull request/issue descriptions, but some processing is done already (…), and if people object, I can trivially drop such changes.
There's one notable directory rename (
platfrom to platform)
I'm not sure how we could merge this one as it modifies practically every file and could break so many things
Happy to split it in any particular way you like
if your system is mostly by top level directory, i can split by that
(i don't have a lot of time today, and won't have more time before Sunday, but I'm in no hurry)
@user you wanted to comment 😉
Hi, thank you for fixing all the grammar mistakes😊
Would be much easier to merge if we split code changes from the docs🙏
is that something i can distinguish by file extension or path? (i have ~2 hr before next week)
I'll try a simple split of
platform/ vs docs/ + README.md@user is that split enough? The original PR no longer includes the docs changes.
@user
thank you! Merged!
🔥
Do you want me to look through the other PR for things? Each commit in a PR is a specific change, so if a certain category is undesirable, I can drop it. I generally check to see if an unhyphenated word is used before suggesting it (and I skip flavors that aren't used). I can, of course, skip changelogs...