Even without deep technical knowledge, as a senior tech recruiter with 30 years of experience, there are several things I'd be looking for in a candidate's GitHub repository. These are primarily indicators of the candidate's activity, commitment, and interactions with the tech community:

### Important Aspects:

1. **Commit Frequency:** How often are they committing? Regular contributions might indicate consistency and a continuous effort to improve or maintain their projects.

2. **Repository Documentation:** Is there a README file in the repository? Does it clearly explain what the project is, how to set it up, and its purpose? Clear documentation suggests the developer values clarity and understands the importance of making their work accessible to others.

3. **Issue Tracking & Resolution:** How does the candidate respond to issues opened by others? Are they courteous, timely, and effective in their responses?

4. **Pull Requests:** Has the candidate contributed to other projects or have others contributed to theirs? This can show collaboration and their ability to work in a team environment.

5. **Code Comments:** Even without technical expertise, you can gauge if they've added comments to their code. This suggests they're considering the next developer who might work on or review their code.

6. **Diverse Portfolio:** A variety of projects can indicate a breadth of skills or interests. For certain roles, you might want a specialist, but for many positions, a generalist can be invaluable.

7. **Stars and Forks:** These can be indicators of the popularity or utility of a repository. If a project has many stars, it's often a sign that the community finds it valuable.

### Less Important Aspects:

1. **Languages Used:** While it's useful to see the languages the developer is familiar with, it’s more about how they use them. Some amazing projects can be done in 'simpler' languages.

2. **Number of Followers:** While it can indicate influence or networking, it doesn't directly correlate with coding ability or suitability for a particular role.

3. **Profile Aesthetics:** Some developers spend time making their GitHub profile look aesthetically pleasing with charts, graphics, etc. This can be fun, but it's not a direct indicator of their coding skills.

### Completely Unimportant:

1. **Join Date:** Just because someone joined GitHub recently doesn’t mean they are inexperienced. They might have been coding for years before joining.

2. **Contribution Streaks:** Seeing that a developer coded every day for a year can indicate passion or commitment, but it's not a definitive sign of skill. Moreover, it's essential to prioritize work-life balance, and continuous streaks might not always be healthy.

3. **GitHub Profile Picture:** Whether they have a professional photo, an avatar, or no picture at all, this has no bearing on their technical capabilities.

When reviewing a GitHub profile, the broader picture is essential. A combination of factors will provide insights into the candidate's skills, work habits, and compatibility with your team's needs.