issues
search
magicstone-dev
/
c4-tools
Maintaining community-driven forks using the Collective Code Construction Contract (C4)
GNU General Public License v3.0
8
stars
1
forks
source link
issues
Newest
Newest
Most commented
Recently updated
Oldest
Least commented
Least recently updated
Add script to show downstream forks
#19
weex
closed
2 years ago
0
Problem: There's no easy way to see downstream of a fork of an upstream project with many forks
#18
weex
closed
2 years ago
0
Problem: Periodic sync of upstream PRs isn't documented
#17
weex
opened
2 years ago
0
add UpstreamPR####
#16
weex
closed
2 years ago
0
Update CONTRIBUTING.md
#15
weex
closed
2 years ago
0
Problem: No mention of addendum in Contributing
#14
weex
closed
2 years ago
0
Problem: C4Social should have a motivating rallying cry
#12
ledcoyote
closed
2 years ago
5
Problem: Resolving upstream fetches that have conflicts may result in broken build
#11
weex
opened
2 years ago
2
Problem: Pulling in upstream PRs requires command-line
#10
weex
opened
2 years ago
0
update to use .yml file stored in each repo
#9
weex
closed
2 years ago
0
Problem: The script only works for one project
#8
weex
closed
2 years ago
0
Problem: Nothing links to the fork bring-up doc
#6
weex
closed
2 years ago
0
link setup.md to readme
#5
weex
closed
2 years ago
0
add bring-up process
#4
weex
closed
2 years ago
0
abort on upstream merge conflict
#3
weex
closed
2 years ago
0
Problem: branch is pushed even in case of conflicts
#2
weex
closed
2 years ago
0
Problem: local gets out of sync on upstream branch with conflicts
#1
weex
closed
2 years ago
1