Giter VIP home page Giter VIP logo

gamesphere-multiplayer / packabunchas Goto Github PK

View Code? Open in Web Editor NEW
29.0 1.0 37.0 17.19 MB

You are Spacey, from the PACKABUNCHAS, a group of space rangers specialized in packing and rescuing creatures around the galaxy!

Home Page: https://chromegaming.github.io/PACKABUNCHAS/

License: MIT License

JavaScript 76.68% HTML 15.65% CSS 7.68%
chromegaming clue game cussel gaemsphere packabunchas

packabunchas's Introduction

PACKABUNCHAS

Gif

About Our Project ๐Ÿ’ป




Game Description ๐ŸŽฎ

To every game enthusiast, here in PACKABUNCHAS you are spacey, a group of space rangers specialised in packing and rescuing creatures around the galaxy! This is a stimulating brain game Built using core tech-stacks HTML and JavaScript that requires strategy and spatial intelligence. Players must strategically drag different shaped pieces onto the spaceship grid and aim to save the creatures! ๐Ÿš€

Features ๐Ÿ“ƒ

  • Variety of Modes: Standard play mode with time constraints or a relaxing Zen mode.
  • Invertible block pieces: Rotate or flip your pieces for enhanced control over piece placement.
  • Drag Mode: Provides additional strategic opportunities by allowing movement of already placed blocks.
  • Interactive: This game is completely user interactive and friendly with amusing backgrounds, music, and features.


How to make a PR in a Project ๐ŸŸข

If you are interested to contribute in this project how to start contribute

  1. Fork the repo.

  2. After forking, clone the repo to your local machine. To clone the repo to your local machine, run the following command in your terminal:

    git clone https://github.com/<your-github-username>/PACKABUNCHAS
  3. Add a remote upstream to the original repo. To add a remote upstream, run the following command in your terminal:

    git remote add upstream https://github.com/Durgesh4993/PACKABUNCHAS/
  4. Create a new branch. To create a new branch, run the following command in your terminal:

    git checkout -b <your-branch-name>
  5. Make changes in source code.

  6. Add your changes To add your changes, run the following command in your terminal:

    git add <File1 changed> <File2 changed> ...
  7. Commit your changes. To commit your changes, run the following command in your terminal:

    git commit -m "<your-commit-message>"
  8. Push your changes. To push your changes, run the following command in your terminal:

    git push origin <your-branch-name>
  9. Create a PR.


Alternatively Using GitHub Desktop

  1. Open GitHub Desktop and log in to your GitHub account.

  2. Make sure you are on the "Current Repository" view. If not, go to "File" and select "Add Local Repository" to add your repository.

  3. In the "Current Repository" view, ensure you are on the branch that you want to submit a pull request for. If you're not on the correct branch, use the "Branch" menu to switch to the correct branch.

  4. Once you're on the correct branch, make your changes and commit them to the branch. You can do this by clicking the "+" button in the upper-left corner of the GitHub Desktop window, making your changes, and then entering a commit message.

  5. After you've made your changes and committed them, click the "Push origin" button in the top-right corner of the GitHub Desktop window. This will push your changes to the remote repository on GitHub.

  6. Now, go to the GitHub website, navigate to your fork of the repository, and you should see a button to "Compare & pull request" between your fork and the original repository, click on it.

  7. On the pull request page, you can review your changes and add any additional information, such as a title and a description, that you want to include with your pull request.

  8. Once you're satisfied with your pull request, click the "Create pull request" button to submit it.

Note: In order to create a pull request, you must have a fork of the original repository in your GitHub account and you must have made the changes in that forked repository.


Open Source Programs

This project is part of GirlScript Summer of Code. We welcome contributions from the community to help enhance PACKABUNCHAS.

Community


Code of Conduct

Please note that this project is released with a Contributor Code of Conduct. By participating in this project you agree to abide by its terms.


Contact Us

https://www.linkedin.com/in/durgesh4993/

License

This project is licensed under the MIT License.


Contributors

Thank you for contributing to our project! Your support is invaluable in enhancing PACKABUNCHAS. ๐Ÿ˜Š

packabunchas's People

Contributors

aditiprabhakar avatar aditya-bhaumik avatar anshgautam-github avatar anupsimha avatar ayushvishwakarma04 avatar deekshithapalla avatar devanshpaliwal avatar durgesh4993 avatar ishap11 avatar jagjeetchauhan avatar khushipawar37 avatar manaregr8 avatar meetjain1 avatar niyatizzz avatar pankaj-bind avatar priyamjain1105 avatar ramakrushnabiswal avatar unnati-gupta24 avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar

packabunchas's Issues

[Enhancement]: Improve Clarity of Instructions and Descriptions of Different Game Modes

Do you want to have the enhancement of existing game ? ๐Ÿ˜€ Describe yourself..

The current website lacks clear instructions and descriptions for various game modes, which can be confusing for new users.

Game_Mode.mp4

Describe the solution you'd like

The game should offer clear descriptions for each game mode to ensure users understand the purpose and objectives of each mode.

I am a GSSoC'24 contributor and want to contribute to this issue.

Select program in which you are contributing

Other

Code of Conduct

Missing CONTRIBUTING.md File in Repository

Describe the bug โœ๏ธ

The repository currently lacks a CONTRIBUTING.md file, which is an important resource for guiding potential contributors on how to engage with the project effectively. A CONTRIBUTING.md file outlines the contribution guidelines, coding standards, and procedures for submitting pull requests, thus streamlining the contribution process and ensuring consistency across contributions.

Provide step by step information reproduce the bug ๐Ÿ“„

I need to create a CONTRIBUTING.md file tailored to our project's specific needs and guidelines. This file should include information on how to contribute, coding conventions, testing procedures, and any other relevant guidelines for potential contributors. By providing this information upfront, we can lower the barrier to entry for new contributors and ensure that contributions align with project standards.

Select program in which you are contributing

GSSoC24

Code of Conduct

[New Feature]: Fixing the main page

๐ŸŽฎ feature Request

I would like to first add padding to make the elements more ordereded and also add title of the game and a git hub link to the repo and some good background to make the website better
image

Point down the features

feature points

Select program in which you are contributing

GSSoC24

Code of Conduct

Learn.md [Documentation Bug]:

Describe the bug โœ๏ธ

learn.md file is missing in our repository currently @Durgesh4993 sir assign this issue to me I will add it

I am working under gssoc24

Provide step by step information reproduce the bug ๐Ÿ“„

will add the file to the repository

Select program in which you are contributing

No response

Code of Conduct

Girlscript Summer of Code Introduction/Tracking

๐Ÿ‘‹ Hi @GameSphere-MultiPlayer,

I am Prince,web developer(Core Team) Girlscript Summer of Code. I'll be collaborating with you on preparing your repo for GSSoC'24 Program

Why are these changes required?
After Analysing last year's contributions and feedback it would be great for students to have a couple of standard readme files on the repo to understand what the project is all about and some issues detailing what they can contribute. This will help you to see increased engagement in your repository as well.

As mentioned students get a chance to learn step by step, how to build this project as well as invite mentors to collaborate and add features to this repo. I will generate issues, which will provide guidance on how to prepare your repo for Girlscript summer of code 2024 on 10th May.

This issue will serve as a tracking issue to track all issues related to GSSoC'24. I recommend creating a new branch for every issue and opening a pull request to track changes so we can effectively collaborate with each other and merge changes when you and I feel like those changes are ready to be merged on your primary branch.

If you have any questions or concerns, please feel free to leave a comment on this issue or any of the other issues that are generated.

I look forward to working with you :octocat:

[Bug]: Bottom-corner issue

Give a brief about the bug โœ๏ธ

Description
If you see closely, you will find out that the canvas color is spreading out of the canvas screen.
gnfgn

What is the expected behavior? ๐Ÿค”

Description
The canvas colors must be inside canvas.

Provide step by step information reproduce the bug ๐Ÿ“„

Description
I will apply border radius to resolve this issue.

Please assign me this issue.

Select program in which you are contributing

GSSoC24

Code of Conduct

[New Feature]: Auto Commenting Feat for Issue Creation

๐ŸŽฎ feature Request

When issues are created in a project, it is important to provide immediate acknowledgment and guidance to the issue creator. However, manually commenting on every newly created issue can be time-consuming for maintainers, leading to delays and inconsistency in communication.
I would like an automated feature that posts a predefined comment on an issue as soon as it is created. This comment could include acknowledgment of the issue, guidelines for further steps, or any other relevant information. The automation should be customizable to accommodate different project workflows and communication styles.

issue creation

Point down the features

This feature aims to address the problem of delayed and inconsistent communication following the creation of issues. By automatically commenting on issues as soon as they are created, it ensures that contributors receive immediate feedback and acknowledgment for their efforts. This fosters a positive and supportive environment for collaboration, encouraging continued participation and engagement from contributors.

Select program in which you are contributing

GSSoC24

Code of Conduct

Add Topics

In GSSoC'24, GitHub Topics will help the discoverability of your project.

I see that you already have great topics on your repository!
I would recommend adding the name of the company like the software you use to build like "vs-code, ghdesktop" to improve your discoverability.

If you are happy with the topics you have, feel free to close this issue. ๐Ÿ‘

[Documentation Bug]: Add GitHub Desktop Contribution Instructions

Describe the bug โœ๏ธ

The detailed instructions to contribute using GitHub Desktop are missing.

Provide step by step information reproduce the bug ๐Ÿ“„

I am interested in contributing to the project by adding detailed instructions on how to contribute using GitHub Desktop.

I believe that by providing clear and comprehensive guidance, we can encourage more contributors to participate in the project, especially those who prefer using GitHub Desktop for their contributions.

Could you please assign me the issue related to adding GitHub Desktop contribution instructions under gssoc24? I am excited about the opportunity to contribute to the project and help streamline the contribution process for others.

Select program in which you are contributing

GSSoC24

Code of Conduct

[New Feature]: Automated Greeting Workflow

๐ŸŽฎ feature Request

I propose to create a GitHub workflow named "Greetings". This workflow will automatically greet users who create new issues or pull requests in this repository. The Greeting will look like "Hi there! Thanks for opening this issue. We appreciate your contribution to this open-source project. We aim to respond or assign your issue as soon as possible."

Please assign this issue to me

Point down the features

image

Select program in which you are contributing

GSSoC24

Code of Conduct

[New Feature]: Auto Commenting feature for PR Raised

๐ŸŽฎ feature Request

When contributors raise pull requests (PRs) in a project, it is crucial to provide immediate acknowledgment and feedback to encourage collaboration and maintain transparency. However, manually commenting on every PR can be time-consuming for maintainers, leading to delays and inconsistency in communication.
This solution introduces a new GitHub Actions workflow that automatically comments on new and updated pull requests. This feature aims to streamline the contribution process by providing contributors with immediate feedback and guidance upon creating or updating their pull requests.

PR raised

Point down the features

This feature aims to address the problem of delayed and inconsistent communication following the raising of PRs. By automatically commenting on PRs as soon as they are raised, it ensures that contributors receive immediate feedback and acknowledgment for their efforts. This fosters a positive and supportive environment for collaboration, encouraging continued participation and engagement from contributors.

Select program in which you are contributing

GSSoC24

Code of Conduct

Add a Title Section and Footer Section

๐ŸŽฎ feature Request

I suggest adding a "Title Section" and "Footer Section" to the game interface. The "Title Section" will display the game title prominently at the top of the screen, enhancing the overall visual appeal and providing clear identification of the game. The "Footer Section" will include important information such as copyright details, credits, and acknowledgments, allowing players to easily access this information during gameplay.

Please assign this task to me.

Point down the features

Features:

  • Display the game title prominently at the top of the screen.
  • Include a footer section with copyright information, developer credits, and acknowledgments.
  • Ensure the Title and footer is accessible and remains visible across different game screens.

Select program in which you are contributing

GSSoC24

Code of Conduct

[New Feature]: Adding light and dark themes.

๐ŸŽฎ feature Request

feature logic and basic description
The original theme of the game is too bright, i would like to add dark theme to the application.

image

Point down the features

feature points
Dark theme makes the game more user appealing.

please assign this issue to me.

Select program in which you are contributing

GSSoC24

Code of Conduct

[Bug]: Adjusting Font size of the elements in Footer section.

Give a brief about the bug โœ๏ธ

In the Footer Section, the font size of the "PRIVACY NOTICE|TERMS OF SERVICE |[COOKIES INFO]|[CHROME GAMING]" are large and not correctly assigned horizontally.

What is the expected behavior? ๐Ÿค”

I would like to decrease the font size and also to align them such that there is a equal space between the vertical slashes and text.

Provide step by step information reproduce the bug ๐Ÿ“„

Description

Select program in which you are contributing

GSSoC24

Code of Conduct

[Question]:

Describe your question or ask for support.โ“

Description

Select program in which you are contributing

No response

Code of Conduct

[Enhancement]: Adding correct icons to buttons

Do you want to have the enhancement of existing game ? ๐Ÿ˜€ Describe yourself..

Game enhancement The current home icon "<" doesnt provides the clarity of what it does and it feels like back button.
and the full screen icon should change its shape on clicking it once. The full screen and minimize should be different in visibility.

Describe the solution you'd like

Solution steps
A correct home button would be nice with the home icon SVG.

Screenshot 2024-05-31 145757

The full screen icon should change to minimize icon once clicked.

Screenshot 2024-05-31 150538

I can handle this issue. Kindly assign it to me under GSSoC'24.

GSSoC'24 is not in the program list.

Select program in which you are contributing

Other

Code of Conduct

[Enhancement]: Improve the color selector styling

Do you want to have the enhancement of existing game ? ๐Ÿ˜€ Describe yourself..

Screenshot (99)

i can improve the styling of this color panel, i can style it according to the theme of the game, also once it opens up, it does not close back unless the page is reloaded.

Describe the solution you'd like

Solution steps

Improve styling, adding borders and more enhancing styles to the buttons to make it look more interactive.

Select program in which you are contributing

No response

Code of Conduct

Game description under readme section

Describe the bug โœ๏ธ

Hii adding the game description can enhance the readme section and also allow users to get an idea on how the game works

Provide step by step information reproduce the bug ๐Ÿ“„

I would like to add step by step procedure on enjoying the game and wish to to contribute to this project under gssoc'24

Select program in which you are contributing

GSSoC24

Code of Conduct

[New Feature]: Introduction of PACKABUNCHAS Homepage

๐ŸŽฎ feature Request

feature logic and basic description:
We propose implementing a homepage specifically tailored for PACKABUNCHAS. This homepage will serve as a central point for players to access essential game information, interesting facts, and a leaderboard displaying top scores.

Point down the features

feature points:

  1. Game Information Section: The homepage will provide a brief overview of PACKABUNCHAS, including its gameplay mechanics, and key features. This section aims to give players a quick understanding of what the game entails and why it's worth playing.

  2. Fun Facts Segment: Players will discover intriguing facts about PACKABUNCHAS, such as development insights and notable achievements. These fun facts add an element of surprise and entertainment for players, encouraging them to explore the game further.

  3. High Scores Leaderboard: A prominent feature of the homepage will be the leaderboard showcasing the highest scores achieved by players. This leaderboard fosters healthy competition among players, motivating them to improve their skills and strive for the top spots.

  4. Main Game Page Section: An additional section will provide a direct link to the main game page, allowing players to seamlessly transition to the full game experience. This ensures that players have easy access to the game itself, where they can dive deeper into gameplay and engage.

Select program in which you are contributing

GSSoC24

Code of Conduct

[New Feature]: About section

๐ŸŽฎ feature Request

Every game must has a about section in which it has a description about the game or a brief summary on how to play the game, what the game is about and how many modes or levels are there , how r the users going to get the points.

Point down the features

Thf above mentioned points will make the user experience more enhanced because once the user enters a game he looks for the steps to play a game.I will write a little documentation about the game and add an about section in the home page of the game. I will make sure to include all the required points and screenshots of the game which are required priorly.

Select program in which you are contributing

GSSoC24

Code of Conduct

[New Feature]: Workflow for Closing Old Issues

๐ŸŽฎ feature Request

Over time, repositories can accumulate a large number of open issues, including some that may no longer be relevant or actively worked on. Manually closing these old issues can be time-consuming and tedious.

I would like a workflow that automatically identifies and closes old issues based on certain criteria, such as no recent activity or being open for a specific duration.

Point down the features

This feature aims to automate the process of managing old issues, ensuring that the repository remains organized and focused on relevant tasks. By automatically closing old issues, it reduces manual overhead for repository maintainers and helps keep the issue tracker tidy and up-to-date.

Select program in which you are contributing

GSSoC24

Code of Conduct

[New Feature]: Implement Gradient Theme Button

๐ŸŽฎ feature Request

Implement a feature that allows users to customize the background into a gradient theme of their choice.
This includes a gradient theme button that opens a selector for choosing gradient colors and direction, enhancing the visual appeal and user experience of the game.

Feature Logic

Upon clicking the gradient theme button, users are presented with a gradient selector container, where they can choose two colors and the direction of the gradient. This container allows for easy customization of the game's background gradient.

Once the user selects their desired gradient, it dynamically applies to the entire background of the game page, enhancing the visual appeal and personalization of the gaming experience.

The gradient theme button will be strategically positioned at the top right corner of the page, ensuring it does not disrupt gameplay. Overall, this feature aims to empower users with the ability to tailor the game's appearance to their preferences, fostering a more engaging and enjoyable gaming environment.

Point down the features

Feature points

Gradient Theme Button:

A button with a ๐ŸŽจ icon located at the top right corner of the page.
The button should be prominently visible and large enough for easy interaction.

Gradient Selector Container:

Appears when the gradient theme button is clicked.
Contains color pickers for selecting two gradient colors.
Includes a dropdown menu for selecting the direction of the gradient.
Styled to match the overall theme of the game interface.

Gradient Application:

Dynamically applies the selected gradient to the entire background of the game page.
Updates the background gradient in real-time as the user makes selections.

Visibility Toggle:

The gradient selector container should be hidden by default.
Clicking the gradient theme button toggles the visibility of the selector container.

Motivation:

Enhance User Experience: Allowing users to customize the background gradient will provide a more engaging and personalized gaming experience.

Context

Current State: The game currently has a static background color that does not allow any user customization.

Select program in which you are contributing

GSSoC24

Code of Conduct

[New Feature]: feedback page addition

๐ŸŽฎ feature Request

feature logic and basic description
customer rating or feedback will be included in this

Point down the features

feature points
will have qs like how would they rate this and all and ask for any difficulties

Select program in which you are contributing

GSSoC24

Code of Conduct

Add templates for issues

Issue templates are very helpful for a collaboration repo. When users identify a bug or want to add a new feature, you can provide templates so you can collect all the pertinent information you need to fix a bug or add a new feature.

We recommend creating a โ€œReport Bugโ€ and โ€œFeature Requestโ€ issue template.
you can refer this: https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository

Some suggested prompts/questions you can add to a โ€œReport Bugโ€ template are:

Briefly describe the bug
What is the expected behavior?
Please provide step by step instructions on how to reproduce the bug
Some suggested prompts/questions you can add to a โ€œFeature Requestโ€ issue template are:

Briefly describe your feature request
What problem is this feature trying to solve?
How do we know when the feature is complete?

Reference: https://github.com/Recode-Hive/Stackoverflow-Analysis/issues/new/choose
Click on Get Started button and copy the template to your

Logo in the title bar

๐ŸŽฎ feature Request

image

In the title section, it would look much good if I put the logo of the game over there, it will give it a more of professional look.

Point down the features

LOGO IN THE TITLE BAR

Select program in which you are contributing

GSSoC24

Code of Conduct

Readme.md [Documentation Bug]:

Describe the bug โœ๏ธ

Readme.md file can be more interactive and fascinating ,
currently our readme.md file is not upto the mark it needs some changes to attract contributors to our project changes like

@Durgesh4993 sir assign this issue to me I will make it . Thankyou

Provide step by step information reproduce the bug ๐Ÿ“„

Working video of our project, contributors section , allignment fix and some snapshots of our project will make our readme file good.

Select program in which you are contributing

Gssoc24

Code of Conduct

[New Feature]: Preloader

๐ŸŽฎ feature Request

feature logic and basic description
I would like to add a preloader it would be a animation that will render until the page is being loaded

Point down the features

feature points
It would be responsive and matching the theme of UI

Select program in which you are contributing

GSSoC24

Code of Conduct

requirements.txt

Describe the bug โœ๏ธ

I want to add requirements section to the project assign me

Provide step by step information reproduce the bug ๐Ÿ“„

Description

Select program in which you are contributing

No response

Code of Conduct

Missing Code of Conduct File in Repository

Describe the bug โœ๏ธ

Currently, the repository lacks a Code of Conduct file, which is an essential component for fostering a healthy and inclusive open-source community. A Code of Conduct serves as a guideline for expected behavior, ensuring that contributors and participants feel safe, respected, and valued within our community space.

Kindly assign me this issue, so i can work towards it under GSSOC 24

Provide step by step information reproduce the bug ๐Ÿ“„

We need to create a Code of Conduct file and integrate it into our repository. This file should outline expected behaviors, consequences for violating the Code of Conduct, and procedures for reporting incidents. Additionally, it should align with recognized open-source community standards, such as the Contributor Covenant, to ensure comprehensiveness and inclusivity.

Tasks:

Research and select an appropriate Code of Conduct template (e.g., Contributor Covenant, Citizen Code of Conduct).
Adapt the selected template to fit the specific needs and values of our community.
Create a new file named "CODE_OF_CONDUCT.md" or similar in the repository root directory.
Populate the file with the finalized Code of Conduct content.
Update the repository documentation and contributing guidelines to reference the Code of Conduct.
Communicate the implementation of the Code of Conduct to the community through appropriate channels (e.g., README.md, community forums, social media).

Select program in which you are contributing

GSSoC24

Code of Conduct

[New Feature]: Design the Login page and Signup page

๐ŸŽฎ feature Request

Developing secure and user-friendly login and signup pages is crucial for our web application. These pages will enable users to create accounts and authenticate securely, enhancing the overall user experience. Implementing strong security measures, such as input validation and HTTPS, will protect user data and maintain application integrity.

Point down the features

The login and signup pages will feature user-friendly forms for registration and authentication, including fields for username, email, and password, along with client-side and server-side validations. Security measures such as HTTPS, input sanitization, and strong password hashing will be implemented to protect user data. Additionally, options like password visibility toggle, "Remember Me" checkbox, and multi-factor authentication (MFA) will enhance usability and security.

Select program in which you are contributing

GSSoC24

Code of Conduct

[New Feature]: Dark Mode Feature

๐ŸŽฎ feature Request

I want to add a dark mode feature into the game. The color scheme is bright and light by default. I would like to add a new dark color theme so that users can change the theme according to their preference.

Kindly assign this issue to me under "GSSoC'24"

Point down the features

  • Adding a (dark/light) mode toggle button.
  • Implementing a new color scheme (darker) in accordance with the current color scheme.

Select program in which you are contributing

GSSoC24

Code of Conduct

[New Feature]: Auto Commenting feature for PR Merged

๐ŸŽฎ feature Request

When pull requests (PRs) are merged in a project, it is often important to provide consistent feedback or notifications to the contributors. Currently, this process can be manual and time-consuming, leading to inconsistent communication and delayed acknowledgments.

To enhance our communication and acknowledgment process, we're implementing an auto-commenting feature for specific events within our project repository. This feature will automatically generate comments under the following circumstances:
PR Merged: Upon the successful merging of a pull request (PR), an auto-comment will be added to the corresponding issue, indicating that the PR has been merged and expressing gratitude to the contributor for their valuable contribution.

PR merged

Point down the features

This feature aims to solve the problem of inconsistent and delayed communication following the merging of PRs. By automating the commenting process, it ensures that contributors receive timely feedback and acknowledgments. It also reduces the administrative burden on maintainers, allowing them to focus more on code reviews and other critical tasks.

Select program in which you are contributing

GSSoC24

Code of Conduct

Add issues

As the maintainer of a Collaborate repo, keeping Issues up-to-date will help the student community understand what they can do to contribute. Issues should vary by the easy (update documentation) to the difficult (add a new feature). The more involved you are, the more opportunities there are to collaborate.

Recommendations:

Add issues of varying difficulty to the repo often. you must add the tag GSSoC'24, Level 1, Level2, Level 3 good first issue etc.
How we cacluclate the Scores on Leaderboard: Every PR one point
Level 1: 10 points
Level 2: 25 points
Level 3: 45 points
Try to add some documentation issues as well it would be easy for beginner contributor to explore opensource through your repo.
Generate issues even if you plan on solving them, so the repository appears as active.
Contribute/commit often to the repo so it does not go stale.
Reference https://github.com/Recode-Hive/Stackoverflow-Analysis/issues

[Documentation Bug]:

Describe the bug โœ๏ธ

Update of README.md file is required.

Provide step by step information reproduce the bug ๐Ÿ“„

Description

Select program in which you are contributing

GSSoC24

Code of Conduct

There is no CONTRIBUTING.md file in repository

Describe your question or ask for support.โ“

The repository currently lacks a CONTRIBUTING.md file, which is an important resource for guiding potential contributors on how to engage with the project effectively. A CONTRIBUTING.md file outlines the contribution guidelines, coding standards, and procedures for submitting pull requests, thus streamlining the contribution process and ensuring consistency across contributions.

Could you please assign this issue to me under GSSOC 24.

Select program in which you are contributing

No response

Code of Conduct

[New Feature]: Workflow for closing old PRs

๐ŸŽฎ feature Request

Over time, open pull requests (PRs) can accumulate in a repository, cluttering the interface and making it difficult to focus on active development tasks. Additionally, outdated or abandoned PRs may no longer serve their intended purpose and should be closed to maintain repository cleanliness.

Implement a workflow that automatically closes old PRs based on predefined criteria, such as their last update timestamp. By regularly closing PRs that have not been updated within a certain timeframe, the repository can stay organized, and contributors can focus on active and relevant PRs.

Point down the features

This feature aims to automate the management of open PRs in a repository, ensuring that outdated or abandoned PRs are closed in a timely manner. By doing so, it helps maintain repository hygiene, improves workflow efficiency, and provides a better experience for both maintainers and contributors.

Select program in which you are contributing

GSSoC24

Code of Conduct

Learn.md

Learn repos should have a LEARN.md file to teach student how to build your project step by step. You can explain how to build your project with text, code snippets, images, or even short (5 minute) long video lessons. As the maintainer of a Learn repo, the LEARN.md file requires you to think critically about how to explain the building of your project and how to also make it engaging. We don't expect you to be an expert teacher, but we would like you to reflect on how difficult it was to get to your level of knowledge, and then provide friendly guidance to help other students to learn.

Reference: https://github.com/Recode-Hive/Stackoverflow-Analysis/blob/main/Learn.md

[Documentation Bug]:

Describe the bug โœ๏ธ

Describe your bug here

Provide step by step information reproduce the bug ๐Ÿ“„

Description

Select program in which you are contributing

No response

Code of Conduct

Add Code of Conduct

We recommend that every repo has a code of conduct. If you donโ€™t feel comfortable creating your own Code of Conduct from scratch we highly recommend using one of the templates provided by GitHub. If you do use a template, please read through the template and ensure that you can and will abide by the Code of Conduct.

Please follow these instructions on how to add a Code of Conduct.

Sample: https://github.com/Recode-Hive/Stackoverflow-Analysis/blob/main/CODE_OF_CONDUCT.md

[Enhancement]: The first page can be improved.

Hello, I am Anshika, GSSoC'24 contributor. The first page of the application starts the game by clicking anywhere on the screen.

Screenshot 2024-05-13 160102

It can be enhanced by adding a start button in the middle (that space looks empty too) and only starting when the button is clicked. This would lead to more concise and professional gaming experience.

Kindly assign me this issue and I'll get to it right now.

Missing CONTRIBUTION.md file in the Repository

The repository currently lacks a CONTRIBUTING.md file, which is an important resource for guiding potential contributors on how to engage with the project effectively. A CONTRIBUTING.md file outlines the contribution guidelines, coding standards, and procedures for submitting pull requests, thus streamlining the contribution process and ensuring consistency across contributions.

Could you please assign this issue to me under GSSOC 24.

[New Feature]: Auto Commenting when an Issue is Closed

๐ŸŽฎ feature Request

The solution is to automatically post a comment on the issue whenever it gets closed. This comment should thank the issue creator for their contribution and inform them that their issue has been closed. The message can include the issue number and a friendly greeting to make it more personal. This automation ensures that every closed issue receives a consistent and timely response, improving communication and contributor experience.

issue closed

Point down the features

This feature aims to solve the problem of poor communication and lack of acknowledgment when issues are closed. By automatically commenting on closed issues, it ensures that contributors are informed about the closure and are thanked for their efforts. This helps maintain a positive and engaging community atmosphere, encouraging continued contributions and fostering good relationships between maintainers and contributors.

Select program in which you are contributing

GSSoC24

Code of Conduct

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.