Official website for the Ingressive Campus Community, Federal University Lokoja, Kogi State, NG.
View site

About Us

ICAFulokoja is a platform for growth and development of future world-class developers, designers, CTOs, founders and CEOs, to learn from industry subject matter experts, share knowledge, network, build the community and gain from the many great opportunities attached to the program.
We are an active community of tech enthusiasts - including designers and developers committed to building brilliant innovative products.

Our Mission

'Our aim is to create an active environment for tech enthusiasts to learn, share knowledge, network, build their technical skills and equip everyone, regardless of their major, to become world class developers.'

Activities

• Meetups
• Hackathons
• Mentorships
• Code challenges
• Open Source Projects
• Collaboration
• Access to free tools and softwares
• Access to cheap internet and better power supply
• Learning resources for any technical skill
• This activities would help the community members to improve on their skills, learn more, collaborate, experirnce the real world programming and grow faster therby bringing us closer to our mission.
  

Contributor's Guide

Issues can be submitted by anyone, seasoned developers or newbies.

Getting Started

1. If you are new to Git and Github, it is advisable you go through GitHub For Beginners before moving to the next step.

2. Fork this repository, Help Guide to Fork a repository.

3. Clone the project.

   git clone https://github.com/your_username/icafulokoja.github.io.git
   

4. Create a branch specific to the issue you are working on.

   git checkout -b update-readme-file
   

   For clarity to yourself and others on the issue you're working on, name your branch something like update-xxx or fix-xxx where xxx is a short description of the changes you're making. For example update-readme or fix-typo-on-contribution-md.

5. Open up the project in your favourite text editor, select the file you want to contribute to and make your changes.

   If you are making changes to the README.md file, you would need to have Markdown knowledge. Visit here to read about GitHub Markdown and here to practice.

   • If you are adding a new project/organisation to the README, make sure it's listed in alphabetical order.
   • If you are adding a new organisation, make sure you add an organisation label to the organisation name. This would help distinguish projects from organisation projects.

6. After making your changes in the new git branch then add your modified files to git, How to add, commit, push and go.

   git add path/to/filename.ext
   

   You can also add all unstaged files using:

   git add .
   

   Note, using a git add . will automatically add all files. You can do a git status to see your changes, but do it before git add.

7. Commit your changes using a descriptive commit message.

   git commit -m "Brief Description of Commit"
   

8. Push your commits to your Github Fork:

   git push -u origin branch-name
   

9. Submit a pull request.

   Within GitHub, visit this main repository and you should see a banner suggesting to make a pull request. While you're writing up the pull request, you can add Closes #XXX in the message body where #XXX is the issue you're fixing. So an example would be Closes #42 would close issue #42.

Submitting a Pull Request

What is a pull request?

If you decide to fix an issue, it's advisable to check the comment thread in case there's somebody already working on a fix. If no one is working on it at the moment, kindly leave a comment stating that you intend to work on it so other people don't accidentally duplicate your effort.

In a situation whereby somebody decides to fix an issue but doesn't follow up for a particular period of time, say 2-3 weeks, it's acceptable to still pick up the issue but make sure to leave a comment.

Helpful Resources

• Pro GIT Book

• Try Git

• Git/ Git Hub on Windows