Why is there impersonation with "Added Dev Container Folder" commit

Community Cloud
,
1

Something odd happened while I was trying out Streamlit’s Community Cloud. I accidentally clicked “Edit with Codespaces” after connecting my private GitHub repository, and to my surprise, it created an automatic commit called “Added Dev Container Folder” on my main branch.

What bothers me is that it shows up as if I made the commit myself - it used my GitHub email and everything - even though I never actually did this manually. There was no warning of creating this commit as well.

I looked around and found that this same thing has happened to thousands of other GitHub repositories too. (Looks like it’s an undocumented feature of Streamlit Cloud)

Is there a way to make these automatic changes show up as coming from Streamlit’s system instead of making it look like I did it?

It would make more sense since it’s Streamlit’s automated process, not something I chose to do.

Commit History:

image
image1343×321 47.8 KB

2

When you edit with Codespaces, Community Cloud adds a devcontainer file to the repo (if it doesn’t already have one). The file configures the GitHub Codespace to run Streamlit. (Installs Python, your apps dependencies as you declared them for Community Cloud, and runs your app with streamlit run.

3

Correct, why impersonation though? Can’t is be a commit saying streamlit-bot or something added it?

Also, there’s no prompt in the dashboard saying this explicitly right?
Pushing directly to main blocks pushing from local unless you rebase the main commits with local.

4

I’ve asked an engineer if they can answer in more detail about the permission structure used with GitHub’s API.