Skip to content

Pidan/gitignore

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

33 Commits
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

gitignore

a gitignore hub for Pidan.

How to use

Please use it via Pidan

Directory Structure Explanation

- os/              # Directory: Mainly related to the operating system
- language/        # Directory: Mainly related to the programming language
- framework/       # Directory: Mainly related to the development framework
- ide/             # Directory: Mainly related to the integrated development environment (IDE)

How to submit a Pull Request (PR)

Welcome to contribute to this project! If you'd like to submit code changes, please follow these steps:

  1. First, click on the "Fork" button in the top-right corner of the project page. This will create a copy of the project under your own GitHub account.
  2. Next, clone your forked project to your local machine.
  3. Navigate to the cloned project directory.
  4. Add your code changes or modifications in the appropriate folder.
  5. Commit your changes to your local Git repository.
  6. Push your changes to your remote repository.
  7. Finally, browse to your forked project on the GitHub website. You will see a green button that prompts you to submit a PR. Click on it, provide the relevant information and description for your PR, and submit it.

I will review your PR and provide feedback as soon as possible. Thank you for your contribution!

Please note that before submitting a PR, ensure that your local repository is based on the latest version of the main project to avoid conflicts. If necessary, update your local repository and resolve any potential conflicts promptly.

File Naming Conventions

Please note that the files you create should adhere to a naming convention. Each file should follow the format basename.gitignore, where basename represents the system name, programming language, framework, or IDE. Please refer to the existing content for guidance. The extension of the files must be .gitignore.

By following this naming convention, you ensure that the file names have a consistent structure and clearly indicate the purpose and type of the file. Including relevant information in the file name allows others to easily understand the applicable system, language, framework, or IDE, enabling them to use the files correctly.

Please make sure to name the files according to the provided requirements, as it enhances the readability and maintainability of the files.

Issues

If you have any other questions or concerns, please feel free to submit an issue.

License

MIT

Releases

No releases published