KO | EN

GitLite

Minimalist Open Source Repository Search Engine

gitlite — search

#typescript #ai-agents #developer-tools #cli #codex #claude-code #react #mcp #open-source #deepseek-harness #dsh-plugin #ai

BooleanAutocrats

★ 7 Open GitHub ↗

Hacktoberfest 2022 contribution repository!✨ Add your valuable contributions to open source python scripts and much more, tools and projects.

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

# BooleanAutocrats

![image](https://user-images.githubusercontent.com/77196053/195439747-3d2600b0-df06-43fc-9dab-534a9e62616e.png)![Picsart_22-10-07_00-53-27-311](https://user-images.githubusercontent.com/77196053/194401092-6591cde3-887d-4158-b285-0af0065788bd.jpg)

This Repository is a collection of scripts, games, bots, scraper and tools written in python, C, C++, Java, JavaScript etc.

# Prerequisite
 * Python
 * C
 * C++
 * Java
 * JS
 
 # Workflow for execution
  
> Steps

1. Clone the repository
2. Change to any project directory
3. Execute the python script Example:

```
git clone https://github.com/ajcogeek/BooleanAutocrats.git
cd BooleanAutocrats/black_jackgame
python blackjack.py
```

# Workflow for contribution

> Steps

1. Star and fork the repository
2. Clone the repositry

```
git clone https://github.com/<YourUserName>/FunWithPython
```

3. Add a remote for the original repository.
```
git remote add upstream https://github.com/ajcogeek/BooleanAutocrats.git
```
4. Navigate to the project and create a branch.
 ```
cd BooleanAutocrats
git checkout -b <branch name>
```

5. Add/Make the required changes and always fetch upstream changes to avoid merge conflicts
```
git pull upstream master

```
6. Commit the changes.
```
git add <file name(s)>
git commit -m "Change Message"

```
7. Push it to your repository
```
git push origin <branch name>

```
8. Once pushed. check your repository.
9. Clicking on contribute button you can open a pull request.
10. Fill the details and click on Create pull request.

# FAQ!
```
1. Why do merge confilcts occur?
```
> Ans. Suppose you forked the repository, now some other contributor who forked the same repository did some changes and added a PR , the maintainer will check it and finding no visible issues, will merge the PR to the main branch now the repository on your profile is frozen, the updates on the original repository don't reflect on the forked repository of your profile hence dont reflect on your local machine sice you cloned it before the changes. now since you create changes of your own in your local machine, and try to create a PR there will be a merge conflict because the original repository is ahead some changes which are not pulled down and implemented on your local machine,that is the reason of merge conflcits.

```
2. How to avoid merge confilcts?
```

> Ans. when you fork the repository there is a remote usually called 'origin' that is referencing to the forked repository on your profile. you have to add another remote usually called "upstream" that references the original repository , now before making any changes of your own, pull down changes made in the original repository using the command git pull upstream master and then the changes are reflected in your local machine now you can add changes and commit them CONFLICT-LESSLY.

```
3. Do we create another feature branch or work on the main branch?
```
> Ans. Yes, create a feature branch and work on that branch, don't make changes to the main/master branch.

BooleanAutocrats

Explore Similar Repositories

Was this content helpful?

Recent Feedback

Download README