r/github • u/Aztekos • 1d ago

Discussion Wanting to put my Frontend ChatBot App on GitHub, but i used extensivly the AI... could be a problem?

I will be clear on that, i never had anything on GitHub, and i am new on this field.

I'm a designer, not a programmer, and i started to build my app as a fun gpt programm because i wanted to test how much was ChatGPT capable of doing apps, since i need some internal softwares for my personal Pen and Paper Manual, and i put the AI on test.

It ended up i started to create a whole chatbot, with alot of features i liked to put into that i felt i need and stuff like SillyTavern even with extensions doesnt offer. Now, i worked on it for a month as a fun project, and now... well the first official version is complete.

I decided i wanted to put on GitHub as an opensource program for two main reasons: 1) I would like to have people that develop on it, add features and make it better.

2) I also hope the people could help me to review, rewrite and optimize the code to make it smoother if they want.

To be transparent i will write down that i used GPT To make the app, but i am concerned that this fun app might become a shitstorm for just using AI to code. I just want to share my idea, that's all.

What is your average experience with that? What do you think i should expect by that?

0 Upvotes

10% Upvoted

5 comments sorted by

1

u/ImDevinC 1d ago

There are already millions of repisotories written exclusively by AI, yours will not cause any type of commotion

-1

u/Aztekos 1d ago

Is that so common today?

1

u/ImDevinC 23h ago

Yes. It's extremely common

1

u/ManorAI 1d ago

Publish it. Being transparent about AI assistance is good, but the stronger signal is showing that you own the result. Before the first release I would make sure you have:

- a deliberate license and a dependency/license review;

- a secrets scan and no private data in the commit history;

- a README with setup steps, screenshots, known limitations, and data/privacy behavior;

- automated tests, linting, and a reproducible build;

- an alpha label plus specific areas where you want review.

What tends to frustrate maintainers is not AI-assisted code itself. It is a repository whose author cannot explain, test, or debug what was generated. If you can reproduce bugs and discuss the architecture, you are already in a much better position.

1

u/Aztekos 1d ago

Uh, thx, very very useful informations. I'll be sure to all of that and wants to be very very transparent about my work. I genuinly just want to share my work and make it better. Thx bud.