Skip to content

added STM32CubeIDE gitignore #4513

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

yahyayozo
Copy link

Reasons for making this change:

I am an embedded developer using STM32CubeIDE for firmware development, hoping this to be my first pull request. This change introduces a comprehensive .gitignore template specifically tailored for STM32CubeIDE(Eclipse based IDE) projects. It helps streamline version control practices by ignoring unnecessary files like build artifacts and IDE-specific configurations, while allowing teams to decide whether to share certain configuration files (e.g., .launch or .settings).
So my template is a combination to use for Eclipse project with C/C++ language

Links to documentation supporting these rule changes:

I didn't find specific documentation for STM32CubeIDE gitignore settings but this link can help:

This is a simple workshop with STM32CubeIDE, you can check the gitignore file
https://github.com/ethanhuanginst/STM32CubeIDE-Workshop-2019/tree/master

@yahyayozo
Copy link
Author

yahyayozo commented Apr 25, 2025

Any update on this PR? would be so appreciated

# Ignore VSCode configuration files.
# Useful if some team members use VSCode for development.
# If you want to share VSCode settings, comment out the following line.
.vscode/
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@handle We get this quite a bit, but this change is not something that we can accept. The .vscode folder is the workspace folder and is intended to house workspace configuration/settings. We don't want to globally ignore this folder for that reason.
Please read more about the workspace folder here: Workspace settings documentation

Could you please either remove this rule or comment out the line so people can optionally enable the rule?

@wirecat
Copy link
Collaborator

wirecat commented Jun 6, 2025

@yahyayozo got one piece of feedback for you, but otherwise this change looks good to me 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants