[Boost-build] What is the proper workflow to fork library, test, and pull request?

Subject: [Boost-build] What is the proper workflow to fork library, test, and pull request?
From: Tal Lancaster (tal.lancaster_at_[hidden])
Date: 2017-05-25 16:46:11

What is the expected workflow to be able to fork a library, build and test it, and then do a pull request against my changes?  Is this written up anywhere?  So far I haven’t stumbled across it.

I am familiar how to do this for a normal GitHub repository.  But I have run into a number of false starts.

Forked date_time, but I was manually building it and a few of its tests. 
cloned the boost super repo (which did give me everything).  But it isn’t a fork.
Forked boost super repo and cloned forked repo (as I would in a normal project).  But it is missing almost everything.

Steven has pointed out how to go about testing part.  So I think the missing piece is what is the proper way to clone so I will have what I need to be able to build and test a particular library and then perform a pull request?

Thanks.

Tal