Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[build]1.3.1 apparently does not clone dependencies

Open
#248 3 comments 1 reaction 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
cpp
Domain
build-system

Research direction

Inspect the build setup and dependency-fetch step for version 1.3.1, using the 1.2.1 behavior as a comparison. Reproduce a build and check whether dependencies appear in the third_party subdirectory; done means the dependencies are cloned there as they were in 1.2.1.

Written by the indexing model from the issue text.

Description

When launching a build, the dependencies must be cloned into third_party subdirectory. Apparently, that does not occur in 1.3.1. The issue does not exist in 1.2.1

Dominant language
C++
Stars
602
Forks
115
Avg merge
1h 18m
Merged PRs (30d)
110

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from jinja2cpp/Jinja2Cpp

All issues in jinja2cpp/Jinja2Cpp

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.