BSData
linking issues in other subfiles of the same issue
this is a community guideline issue on the ability to fork issues for reference.
Hi @williamcaw I'm not sure what exactly do you want to be able to do.
Could you expand your request a little more?
i have joined this community not as a programmer but as a person just stringing together references of pass ideals or stuff that has been scraped to conjoin items of other information so its not lost . im autistic as of today my mind has been thinking of things that i never want to have and never want to have again. when ever we use the hashtag to reference as a manual fork of information from pass people that have anonymously left data to us for that no longer have control.i do this in my oun free time to make sure that if the question was answered so thay don't have to dig or baggier the people that do programming over and over.
Thank you for the explanation. Under a specific perspective, this sounds like a great idea.
Let me explain why it might have been seen as irritating. Whenever a comment is added for an issue, everyone who participated in it is notified of this new activity. This means that when you cross-reference issues, many people get a lot of notifications, which are not really useful. It does not change an issue, it might be informative for future references, but it is essentially a metadata of doubtful but possible future value.
There is (as of today) no option to selectively unsubscribe from just closed issues (which were mostly where your comments appeared).
So in the end nothing is wrong with what you wanted to do, just the way in interferes with monitoring our issues was really frustrating.
If you're still interested in adding these references, I could grant you admin rights on appropriate repositories and you could edit OPs (opening/original posts) and add references to them directly. Edits do not trigger notifications.